Java Platform Module System: Difference between revisions

Revision as of 14:09, 29 November 2015

Revision as of 07:24, 30 November 2015

Line 28:

== Architecture ==

The Java Module System implemented for Java 9 will include the following [[JDK Enhancement Proposal|JEP]]s and [[Java Community Process|JSR (Java Specification Request)]]:<ref name="jigsaw"/>:

* JEP 200: The Modular JDK: Define a modular structure for the JDK

* JEP 201: Modular Source Code: Reorganize the JDK source code into modules, enhance the build system to compile modules, and enforce module boundaries at build time

Line 46:

| author=Mark Reinhold

| date=2015-09-08

| accessdate=2015-11-29}}</ref>

For example the following module declaration declares that the module ''com.foo.bar'' depends on another ''com.foo.baz'' module, and exports the following packages: ''com.foo.bar.alpha'' and ''com.foo.bar.beta'':

Line 57:

</pre>

Contrary to the Jar file format, the module manifest describes these dependencies, and the JDK is able to check them both at compile-time and runtime. The JDK itself will be modularized for [[Java_version_historyJava version history#Java_SE_9Java SE 9|Java 9]].<ref>{{cite web

| url=http://cr.openjdk.java.net/~mr/jigsaw/ea/module-summary.html

| title=JDK Module Summary

Line 65:

== Links with OSGI ==

The Java Module System does not intend to support all the functionalities that the [[OSGi]] platform currently supports (for example the Life-Cycle model and the Services Registry). However the Java Module System will support functions which are not supported by OSGi, such as modularity at compile-time, and built-in support for native libraries. <ref>{{cite web

| url=http://mreinhold.org/blog/late-for-the-train-qa

| title=Project Jigsaw: Late for the train: The Q&A