You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only if your (existing) project cannot avoid using non-module legacy Jars
20
25
21
-
[Here is a sample](https://github.com/jjohannes/java-module-testing/tree/main/samples/use-all-java-module-plugins)
26
+
[Here is a sample](https://github.com/gradlex-org/java-module-testing/tree/main/samples/use-all-java-module-plugins)
22
27
that shows all plugins in combination.
23
28
24
29
[Full Java Module System Project Setup](https://github.com/jjohannes/gradle-project-setup-howto/tree/java_module_system) is a full-fledged Java Module System project setup using these plugins.
@@ -40,7 +45,7 @@ Add this to the build file of your convention plugin's build
@@ -50,7 +55,7 @@ In your convention plugin, apply the plugin.
50
55
51
56
```
52
57
plugins {
53
-
id("de.jjohannes.java-module-testing")
58
+
id("org.gradlex.java-module-testing")
54
59
}
55
60
```
56
61
@@ -112,3 +117,8 @@ Changes for test runtime (`:test`):
112
117
- Now, the main and test classes are both used as locations for test discovery.
113
118
By this, Gradle will find the `moudle-info.class` of the main module for the tests.
114
119
Using `--patch-module`, _main classes_, _main resources_, _test classes_, and _test resources_ folders are all merged to be treated as one module during test runtime.
120
+
121
+
# Disclaimer
122
+
123
+
Gradle and the Gradle logo are trademarks of Gradle, Inc.
124
+
The GradleX project is not endorsed by, affiliated with, or associated with Gradle or Gradle, Inc. in any way.
0 commit comments