Update (25 March 2020): There has been significant progress towards proper JPMS support. A nightly build of Gradle 6.4 now includes options to develop with Java 9 modules natively. See https://github.com/gradle/gradle/issues/890#issuecomment-603289940 . Update (29 September 2020): Since Gradle 6.4 (current release as of this update is 6.6.1) you can now support JPMS modules natively in … Read more
With the standardization of the HTTP Client API, the incubated APIs are now removed. The module name and the package name of the standard API will be java.net.http which can now be used as – module <yourModuleName> { requires java.net.http; } Also, adding to the tally, the applications, frameworks(like Maven, Gradle etc) or IDEs relying … Read more
Excluding the transitive dependency made it work and adjusting the module-info.java too!!! compile(“org.springframework.boot:spring-boot-starter:1.5.3.RELEASE”) { exclude group: ‘commons-logging’, module: ‘commons-logging’ } compile(“org.springframework.boot:spring-boot-starter-web:1.5.3.RELEASE”){ exclude group: ‘commons-logging’, module: ‘commons-logging’ }
jlink Yes, this is possible with jlink (JEP 282), but all of your code and your dependencies need to be modular JARs (i.e. ones with module-info.class). It works like this: jlink –module-path $JAVA_HOME/jmods:mods –add-modules your.app –launcher launch-app=your.app –output your-app-image In detail: –module-path lists the folders that contain modules – this needs to include the platform … Read more
A requires clause expresses that the required module is needed at compile and run time. Consequently, when the module system encounters such a clause during module resolution (the phase in which module descriptors are processed and dependencies are resolved) it searches the universe of observable modules (the modules in the JDK and on the module … Read more
The modules file is a container file. It’s internal to the JDK and the format is not documented (it may change at any time). For troubleshooting purposes, the jimage tool in the bin directory can be used to list or extract the contents.
The module system has mainly the following impact on the code: A package can only be accessed from one module (Nested packages are treated as separate, so even though the package java.util is in the module java.base, the package java.util.logging can be in the module java.logging) You can only access public fields and methods of … Read more
Here is the migration guide for Java 9, New Class Loader Implementations JDK 9 maintains the hierarchy of class loaders that existed since the 1.2 release. However, the following changes have been made to implement the module system: The application class loader is no longer an instance of URLClassLoader but, rather, of an internal class. … Read more
When compiling an unnamed module, java.xml.bind is not accessible by default, but in a modular project (as in this question) failing to resolve reference to module java.xml.bind was a bug (see edit below). To work around this until the bug is fixed, you can explicitly include module java.xml.bind by double click on Is modular (see … Read more
The module system does not distinguish between production code and test code, so if you choose to modularize test code, the prod.module and the test.module cannot share the same package com.acme.project, as described in the specs: Non-interference — The Java compiler, virtual machine, and run-time system must ensure that modules that contain packages of the … Read more