Java 11 module compatibility about kryo-tools HOT 2 CLOSED

I now better understand the above mentioned "Please don't publish this project to a public artifact repository! " after reading discussion of Jigsaw modules from the heads of Sonatype and Maven: https://dzone.com/articles/java-automodules-considered-bad-for-your-health Here and in other articles they plead for people to completely avoid fully-automatic filename based automodules.

This post: https://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html comes to the conclusion that you should not upload an artifact with a module-info.java to a Maven repository unless all the required modules in that module-info.java also declare a module name, via module-info.java or at least via Automatic-Module-Name in the JAR manifest.

So we should only include the Automatic-Module-Name in the JAR manifest until our dependencies all specify a module name, then we can add a module-info.java. The question is then how we would build the library at all under Java 11 without a module-info.java.

Naming: They suggest all module names should be namespaced and probably based on Maven group+artifact coordinates. Generally, modules should be named in reverse-DNS style like Java packages, and ideally the name of the module is the shortest common prefix of all the packages it exports.

from kryo-tools.

Addressed in v1.5.0.

from kryo-tools.