-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
reactor-core does not declare a stable automatic module name #1641
Comments
The fallback of solving from artifact filename should work with a result of |
@simonbasle since it does not require a JDK update and only a matter of adding a line to the manifest, I support the idea of adding an |
any counter-argument to using these: |
we need to double check that we have no conflicts with the packages. |
right. so far I don't see a split package in Package |
Fixed as part of reactor/reactor#667 in #1692 / f8a2dac |
Expected behavior
Hope
reactor-core-3.2.8.RELEASE
support java9+ modular system!Actual behavior
it does not support java9+ modular system!
Steps to reproduce
use reactor-core in my Jigsaw multi-module maven project, but it does not work.
Next, I inspected the reactor-core-3.2.8.RELEASE jar file,
module-info.java
file.Automatic-Module-Name
attribute in META-INF/MANIFEST.MF file.Reactor Core version
3.2.8.RELEASE
JVM version (e.g.
java -version
)java 11.0.1
The text was updated successfully, but these errors were encountered: