You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tom De Wolf (Jira)" <ji...@apache.org> on 2020/03/30 09:35:00 UTC

[jira] [Created] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

Tom De Wolf created SUREFIRE-1765:
-------------------------------------

             Summary: target/test-classes should not be added to classpath when tests run on modulepath using patch-module
                 Key: SUREFIRE-1765
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1765
             Project: Maven Surefire
          Issue Type: Bug
            Reporter: Tom De Wolf


When running junit tests using the maven-surefire-plugin the target/test-classes are added as first entry in the classpath.

However, when testing a explicit java module with a module-info.java the test-classes are already part of the module path using --patch-module. So they should not be on the classpath?

In some scenario's this can give unwanted side-effects, i.e. that the same classes are on the modulepath and classpath, possibly with a module-info.class in both locations (cfr [https://bugs.openjdk.java.net/browse/JDK-8241770).]

So it seems that it is best that target/test-classes is only added to the classpath when it is not put on the module-path.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)