Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upProvide Automatic-Module-Name #910
Comments
|
For now the low hanging fruit is to declare an "Automatic-Module-Name" in the MANIFEST just like Reactor and Netty have done. I propose using a filename convention which is also what Java's ModuleFinder picks by default:
I am aware of the recommendation to use reverse DNS naming based on the root package but there is quite a bit of divergence on among libraries this including Reactor which uses the filename convention and Netty which uses reverse DNS naming but based on module names rather than packages. Also modules ( |
|
Moving to backlog to allow more time for feedback. |
An
Automatic-Module-Namein the manifest of the published JAR-files would improve Java 9+ compatibility when using modules. Currently you will receive warnings about using an unstable name derived from the module's file name.Motivation
Targeting Java 9+ is becoming more common and being able to use RSocket while also using Java modules would be beneficial to those projects.
Desired solution
Set an
Automatic-Module-Namefor JARs.Considered alternatives
A full
module-info.javafor every project could also be added, but is more complicated while also keeping Java 8 support.