@@ -32,6 +32,29 @@ The plugin supports the following test engines:
3232
3333An example application using this plugin is available [ here] ( https://github.com/java9-modularity/gradle-modules-plugin-example ) .
3434
35+ Compatability
36+ ===
37+
38+ The plugin is compatible with the following Gradle versions:
39+
40+ | Gradle version | Min plugin version | Max plugin version |
41+ | ----------------| ----------------------------------------------------------------------------------------| --------------------|
42+ | 5.* -> 7.5.+ | 1.+ | |
43+ | 7.6+ | See [ issue #258 ] ( https://github.com/java9-modularity/gradle-modules-plugin/issues/258 ) | |
44+
45+ The plugin is compatible with the following Java versions:
46+
47+ | Java version | Min plugin version |
48+ | --------------| --------------------|
49+ | 11+ | 1.0.0 |
50+
51+ The plugin is compatible with the following Kotlin versions:
52+
53+ | Kotlin version | Min plugin version |
54+ | ----------------| --------------------|
55+ | 1.0.* -> 1.6.* | 1.0.0 |
56+ | 1.7+ | 1.8.12 |
57+
3558Setup
3659===
3760
@@ -636,7 +659,7 @@ Using the ModularJavaExec task
636659===
637660The ` application ` plugin can handle only one executable application.
638661To start multiple applications, you typically need to create a ` JavaExec ` task for each executable application.
639- The module plugin offers a similar task named ` ModularJavaExec ` , which helps executing modular applications.
662+ The module plugin offers a similar task named ` ModularJavaExec ` , which helps to execute modular applications.
640663This task automatically configures the JVM with the correct arguments such as ` --module-path ` .
641664It exposes the same properties and methods as the [ ` JavaExec ` ] ( https://docs.gradle.org/current/dsl/org.gradle.api.tasks.JavaExec.html ) task,
642665the only difference being that the module name should also be provided when setting the ` main ` property.
0 commit comments