Revision as of 21:53, 16 March 2019 edit 2a02:aa16:397f:4100:c09b:9c40:28ce:2c27 (talk) fix wrong title for JEP 253 ← Previous edit		Revision as of 06:27, 23 April 2019 edit undo 93.240.108.84 (talk) The module system explicitly does not support versioning. Modules only have names, not versions. You cannot have multiple versions on the module path. It is officially recommended to have versions managed with an external tool like Maven or Gradle. Next edit →
Line 3: \| title=Java Platform Module System (JSR 376) \| publisher=[[Oracle Corporation]] \| accessdate=2018-07-02}}</ref> specifies a distribution format for collections of [[Java (programming language)\|Java]] code and associated resources. It also specifies a repository for storing these collections, or ''[[modular programming\|modules]]'', and identifies how they can be discovered, loaded and checked for integrity. It includes features such as ~~versioning and~~ namespaces with the aim of fixing some of the shortcomings in the existing [[JAR (file format)\|JAR]] format, especially the [[Java Classloader#JAR hell\|JAR Hell]], which can lead to issues such as classpath and class loading problems. The Java Module System was initially being developed under the [[Java Community Process]] as JSR 277 and was scheduled to be released with Java 7.

Java Platform Module System: Difference between revisions