[
https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071163#comment-17071163
]
Tibor Digana commented on SUREFIRE-1765:
----------------------------------------
[~tomdw]
We have another Jira ticket for the same issue.
Run the Maven build in debug mode {{i.e. mvn -X test}} and see the arg file
with all module/class paths and patches. You may want to post how you would
like to have it. First of all, pls see the reality in Surefire which is the
starting point for me. See the console log and see the part before the test is
going to start.
> 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
> Affects Versions: 2.22.1, 2.22.2
> Reporter: Tom De Wolf
> Priority: Major
> Attachments: reproduce-xxxAnnotation-jdk-bug.zip
>
>
> 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)
