-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 9 Automatic Module Name #11
Comments
vy
added a commit
that referenced
this issue
Dec 8, 2019
@pitschr, done, see 66f181e. I have released I have also spent some time to create a multi-release JAR bundle (incl. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When building JAR I noticed warning:
To fix it, you need to update the pom.xml
Add to
<properties />
Add to
<build/>
As it is updating the manifest in JAR file only with
Automatic-Module-Name: com.vlkan.rfos
I expect there should be no problem with Java 8 too.The drawbacks is that currently the Java 9 modules which are consuming your library have currently:
With the entry in manifest the name of plugin will be stabilized for Java 9+ modules and they have to update their
module-info.java
to:then. This is only the drawback. Adding a small comment in readme.md (perhaps a separate section for Java 9+ developers) would be also helpful. Can you please consider it for 0.9.1 release? I'll also add the Java 9+ module name to my library as well.
For further reference you may check out:
https://dzone.com/articles/automatic-module-name-calling-all-java-library-maintainers
The text was updated successfully, but these errors were encountered: