[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258466#comment-16258466 ]
Sven Strohschein commented on SUREFIRE-1262: -------------------------------------------- Ok, I tried to test with 2.21.0-20171119.101941-51, but now I'm facing a problem which I already had with 2.20 (so I had to stay on 2.19.1). It is this issue / incompatibility with JUnit 5: https://github.com/junit-team/junit5/issues/809 > 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 > Fix For: 2.21.0.Jigsaw > > > 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 (v6.4.14#64029)