Java Platform Module System: Difference between revisions

Content deleted Content added
Mark Reinhold, a chief Architect of the Java Platform Group at Oracle in his tweet argues to not name it Java Platform Module System only Java Module System
Arguing for a different name in a tweet is just personal opinion. Let's use the JSR name for now.
Line 1:
The '''Java Platform Module System'''<ref name="Please stop calling it JPMS">{{cite tweetweb
| url=http://openjdk.java.net/projects/jigsaw/spec/
| user=mreinhold
| title=Java Platform Module System (JSR 376)
| number=994669659029999616
| publisher=[[Oracle Corporation]]
| date=10 May 2018
| 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.
| title=Please stop calling it JPMS.
}}</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.