[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089769#comment-17089769 ]
Pavel_K commented on SUREFIRE-1262: ----------------------------------- When maven-compiler-plugin:3.6.2:testCompile compiles my jpms module it shows Classpath and Modulepath and they are correct, because on Modulepath I see the jpms modules I use in my module. However, when maven-surefire-plugin:3.0.0-M4:test is executing I see only test classpath, provider classpath, test(compact) classpath, provider(compact) classpath, in-process classpath, in-process(compact) classpath and all my modules go are listed in test classpath. Are you sure this feature works? Or maybe I must activate it somehow? Could anyone explain? > Add modulepath support > ---------------------- > > Key: SUREFIRE-1262 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1262 > Project: Maven Surefire > Issue Type: Improvement > Reporter: Robert Scholte > Assignee: Tibor Digana > Priority: Major > Fix For: 2.21.0 > > > With the Jigsaw project Java9 is extended with a modulepath. This means that > surefire should be executed in a different way. > When working with a modulepath, the Classpath in the MANIFEST of the > executable jar will be ignored, you need need to add everything on > commandline. > Just like javadoc, the java executable has an {{@<file>}} option, where you > can add arguments per line. So this is the new preferred way to build the > module-path. > IIUC for surefire it is important to add {{--patch-module > target/test-classes}} (was: -Xpatch) which makes it possible to use the same > packages as target/classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)