You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Please add a module-info.java in order to make it a module. #16
I believe the standard approach is to compile everything targeting Java 8, except for the module-info.java file, which should be compiled targeting Java 9+. Then package all the class files in a JAR and publish it.
If the library is used on Java 9+ and placed on the module-path, then the module-info file is used. Otherwise, if the code is placed on the class-path, or is used on Java 8, then the module-info file is ignored.
Activity
lemire commentedon Mar 22, 2019
Could you contribute a PR?
joehei commentedon Mar 24, 2019
done :-)
lemire commentedon Mar 25, 2019
@joehei Thanks for the PR. It seems to break our tests... Presumably the issue is that it breaks backward compatibility with Java 8.
Many users are going to stick with Java 8. It seems unwise to break compatibility with Java 8. Is there a way around this?
tkslaw commentedon Oct 7, 2023
I believe the standard approach is to compile everything targeting Java 8, except for the
module-info.javafile, which should be compiled targeting Java 9+. Then package all the class files in a JAR and publish it.If the library is used on Java 9+ and placed on the module-path, then the module-info file is used. Otherwise, if the code is placed on the class-path, or is used on Java 8, then the module-info file is ignored.
Note this is not the same thing as the multi-release JAR feature.