[MCOMPILER-494] - Add a useModulePath switch to the testCompile mojo (#119)

Co-authored-by: Guillaume Nodet <[email protected]>

Author: dmlloyd

src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java

@@ -161,6 +161,18 @@ public class TestCompilerMojo extends AbstractCompilerMojo {
     @Parameter(defaultValue = "${project.build.directory}/generated-test-sources/test-annotations")
     private File generatedTestSourcesDirectory;
 
+    /**
+     * <p>
+     * When {@code true}, uses the module path when compiling with a release or target of 9+ and
+     * <em>module-info.java</em> or <em>module-info.class</em> is present.
+     * When {@code false}, always uses the class path.
+     * </p>
+     *
+     * @since 3.11
+     */
+    @Parameter(defaultValue = "true")
+    private boolean useModulePath;
+
     @Parameter(defaultValue = "${project.testClasspathElements}", readonly = true)
     private List<String> testPath;
 
@@ -288,6 +300,12 @@ protected void preparePaths(Set<File> sourceFiles) {
             testModuleDescriptor = result.getMainModuleDescriptor();
         }
 
+        if (!useModulePath) {
+            pathElements = Collections.emptyMap();
+            modulepathElements = Collections.emptyList();
+            classpathElements = testPath;
+            return;
+        }
         if (StringUtils.isNotEmpty(getRelease())) {
             if (Integer.parseInt(getRelease()) < 9) {
                 pathElements = Collections.emptyMap();