Move module-info.class to root of jar?

[remkop]

This is a follow-up item for #495.
Having the module-info.class in /META-INF/releases/9/ apparently also has drawbacks.

Charles Nutter reported he had issues after putting the module-info.class in /META-INF/releases/9/ :
https://twitter.com/headius/status/1037931427000725504

So it may be safer to put it in the root of the jar after all. Since we publish two artifacts, old tools that cannot handle Java 9 bytecodes can always use the non-modular picocli.jar.

[Warkdev]

Hi, just revert this commit: 095ea30

Warkdev

[remkop]

Cool, thanks!
I’ll first try to reproduce the problem to see if this is really necessary.

[remkop]

(Note to self) The beryx/badass-jar-plugin has a setting to prevent the creation of a multi-release jar:

jar {
    ...
    multiRelease = false
    ...
}