Java Platform Module System: Difference between revisions

Content deleted Content added
Line 44:
 
Additionally, several other JDK 9 features have been added to ease transition to the module system:
* JEP 238: Multi-Release JAR Files: Extend the JAR file format to allow multiple, Java-release-specific versions of class files to coexist in a single archive.<ref>{{cite web
| url=http://openjdk.java.net/jeps/238
| title=JEP 238: Multi-Release JAR Files
| publisher=[[Oracle Corporation]]
| accessdate=2017-07-31}}</ref>
* JEP 253: Prepare [[JavaFX]] UI Controls & CSS APIs for Modularization: Define public APIs for the JavaFX functionalities that is presently only available via internal APIs and would become inaccessible due to modularization.<ref>{{cite web
| url=http://openjdk.java.net/jeps/253
| title=JEP 275: Modular Java Application Packaging
| publisher=[[Oracle Corporation]]
| accessdate=2017-07-31}}</ref>
* JEP 260: Encapsulate Most Internal APIs: Make most of the JDK's internal APIs inaccessible by default but leave a few critical, widely-used internal APIs accessible, until supported replacements exist for all or most of their functionality.<ref>{{cite web
| url=http://openjdk.java.net/jeps/260
| title=JEP 260: Encapsulate Most Internal APIs
| publisher=[[Oracle Corporation]]
| accessdate=2017-07-31}}</ref>
* JEP 275: Modular Java Application Packaging: The [[Java packager]] will evolve for JDK 9, making it aware of modules, allowing for example to package a module and all the modules it depends on.<ref>{{cite web
| url=http://openjdk.java.net/jeps/275