Skip to content
This repository has been archived by the owner. It is now read-only.
master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

JpmsGradlePlugin

This plugin adds some support for the Java Platform Module System (JPMS) to gradle builds.

NOTE

Gradle 7.0 introduced full support for Jigsaw modules, so you if you are using Gradle 7 or newer, you should think about changing your builds to use the modularization support provided by Gradle.

Applying the plugin

    plugins {
        id "com.dua3.gradle.jpms" version "1.1"
    }

Fixing up test task

For modular JDK 9+ builds, the module under test is patched to include the test classes (best information I have found on this is in this german language article[(https://www.informatik-aktuell.de/entwicklung/programmiersprachen/java-9-das-neue-modulsystem-jigsaw-tutorial.html)].

Since the test library has to be patched in, it's requeired to pass its module name to the plugin. Example for junit5 (this is also the default value):

    jigsaw {
        testLibraryModule = 'org.junit.jupiter.api'
    }

For JDK 8 builds, testing is done on the classpath.

Task moduleInfo to create modularised Jars that are compatible with Java 8

If a module-info.java is present in a Java 8 build, the file is removed from the source set and instead compiled in Java 9 compatibility mode. This makes it possible to use the same Jar file in Java 8 and moduarized Java 9+ buillds.

This task is added automatically when applying the plugin.

In theory, a module-info.java file should be ignored when a Jar is used in a pre-Java 9 build. However some tools (SpotBugs < 3.1.3 being an example) will fail if a module-info is present in a library. As a workaround, you can create a multi-release jar like this:

    jigsaw {
        multiRelease = true
    }

I have also heard but not confirmed myself that the android toolchain chokes if a module-info is present. I'd be glad to hear if setting multiRelease = true solves this.

Eclipse (tested in Oxygen.3a) still has problems when a multi-release jar is used.

Task jlink to create standalone apps

To create standalone applications as described in Steve Perkin's blog, you can use the jlink task like this:

   jigsaw {
        module = 'cli'
        main = 'package.MainClass'
        application = 'cli'
        compress = 2
    }

Task bundle to create application images and installers (BETA - tested on MAC only)

This task depends on the runtime image created by the jlink task. To create an application image use:

    jigsaw {
      type = <either 'image', 'installer', or one of the package types for your platform>
      application = 'application name'
      main = 'package.MainClass'
    }

main can either refer to a class containing a main() method or extending the JavaFx Application class. If type is omitted, an application image is created.

Note that in order to create an installer, the jpackager tool has to be installed on your system.

I will add new features as I need them and find the time.

Fixing Gradle´s 'javadoc' task

When creating JDK-8 compatible jars, module-info.java is removed from javadoc input to prevent errors.

Removing module-info.java from eclipse project if Gradle`s 'eclipse' plugin is used

Eclipse as of version 2018-09 still has problems with JDK 11 and modularized builds. As a workaround, module-info.java will be ignored when creating an eclipse project. You can use eclipse for development, but you should however use gradle from the command line to create artefacts for distribution.

Configuring the module path for the 'run' task

If you use the 'application' gradle plugin and the project contains module-info.java, the option --module-path will be automatically set for the gradle 'run' task.

Importing Gradle projects into Eclipse

I recommend using the eclipse plugin together with this plugin and not using eclipse Buildship. Buildship always messes up the module path again when it thinks it should update the project configuration. If you have a multi project configuration, make sure you use at least version 0.7.1 of the plugin.

In your gradle.build:

    plugins {
      id 'java'
      id 'eclipse'
      id 'com.dua3.gradle.jpms' version '0.7.1'
    }

or for multi project builds where the new mechanism doesn't work:

    plugins {
      id 'com.dua3.gradle.jpms' version '0.7.1' apply false
    }
    
    subprojects {
    
      apply plugin:  'java'
      apply plugin:  'eclipse'
      apply plugin:  'com.dua3.gradle.jpms'
      
      ...
    }

Then create/update the eclipse project configuration:

    gradlew cleanEclipse eclipse

Issues with GitLab Auto DevOps

The Auto Test on GitLab Auto DevOps failed when this plugin was loaded because Gradle was run with Java 8. I changed the plugin in the meantime so that simply loading the plugin should not make any issues as long as no module-info.java is present and compatibility is set to Java 8.

This solved part of the problem in that plugin loading succeeds now. However the plain old compileJava task fails because only Java 8 is supported in the default configuration; the JDK 11 Dockerfile used for compilation was not used in Auto Test.

If you run into this problem, just put a file called system.properties into the root folder of your project to tell heroku which JDK to use:

    java.runtime.version=11

Example project

Have a look at the fxbrowser project for an example on how to build a non-trivial standalone application using the plugin.

Enabling debug output

Set the environment variable DEBUG_JPMS_GRADLE_PLUGIN. If you are using Gradle in daemon mode, make sure to stop the daemon after changing the environment.