Auto-modules vs. the unnamed module

Ceki Gulcu ceki at qos.ch
Thu Apr 27 14:58:04 UTC 2017


Hello all,

Please forgive my possibly silly question but can someone kindly explain 
  the advantages of placing a non-modular artifact on the module path 
instead of the class path? In other words, why should the user prefer a 
non-modular artifact to act as an auto-module instead of its packages 
being merged with the unnamed module?

If there are no major advantages for placing an non-modular artifact on 
the module path instead of the class path, then auto-modules serve no 
real purpose and otherwise just increase entropy.

What am I missing?

--
Ceki Gülcü


More information about the jigsaw-dev mailing list