Pluggability of automatic module name/version

[Paul Benedict]

Dear EG members,

One concern I have with finding automatic modules [1] is the algorithm,
which determines the automatic module name and version, is baked into the
JDK. It appears to me this should be pluggable through a service so that it
could be customized. Although we can speculate what will happen with EE 8
and modules [2], pluggability would allow alternate implementations to
perform custom naming/version based on other criteria.

Such criteria, for example....
*) The GAV specified in META-INF/maven/.../pom.xml embedded in many Maven
artifacts [3].
*) JBoss modules metadata from the EAP/WildFly shared modules directory
[4].
*) WebSphere's shared libraries might also be applicable to this situation
[5].

References:
[1]
http://download.java.net/java/jigsaw/docs/api/java/lang/module/ModuleFinder.html#of-java.nio.file.Path...-
[2] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-March/006795.html
[3] https://maven.apache.org/guides/mini/guide-archive-configuration.html
[4] https://docs.jboss.org/author/display/WFLY8/Class+Loading+in+WildFly
[5]
http://www.ibm.com/support/knowledgecenter/was_beta/com.ibm.websphere.base.doc/ae/tcws_sharedlib_create.html

Cheers,
Paul