[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258475#comment-16258475
]
Sven Strohschein commented on SUREFIRE-1262:
--------------------------------------------
Ok, It seems nobody has get surefire 2.20 and beyond get working together with
JUnit 5, so I have to wait until the JUnit 5 problem is fixed (or should I now
immediately join the JUnit 5 team to fix that bug? ;-)). Maybe I could test the
surefire snapshot version in combination with JUnit 4.12.
> 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)
