If the JAR for this repo is used in a project where the module system is
active, Java treats any "plain JAR" without a module descriptor as an
"automatic module" and allows it to be used by other modules in the
application.
For instance, a module in an application using JPMS can depend on this
project like
Defining an Automatic-Module-Name allows for explicitly controlling
the name that modules use when loading your automatic module, rather
JPMS guessing at the automatic module name for the JAR based on the
JAR's filename.
Alternatively we could add a module-info.java to this project to
enable it to be loaded as a regular (not automatic) module but that
would also require increasing the compiler target from 8 to 9.
If the JAR for this repo is used in a project where the module system is active, Java treats any "plain JAR" without a module descriptor as an "automatic module" and allows it to be used by other modules in the application.
For instance, a module in an application using JPMS can depend on this project like
Defining an
Automatic-Module-Name
allows for explicitly controlling the name that modules use when loading your automatic module, rather JPMS guessing at the automatic module name for the JAR based on the JAR's filename.Alternatively we could add a
module-info.java
to this project to enable it to be loaded as a regular (not automatic) module but that would also require increasing the compiler target from 8 to 9.Closes #82