[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258491#comment-16258491
]
Tibor Digana commented on SUREFIRE-1262:
----------------------------------------
[~novanic]
Please understand that JUnit 5 has to adapt to our API. I know the JUnit team
and I would say the team does not want to support surefire provider in their
code base, but be sure that our team will take over the code from JUnit 5 team
and we will do so!
The question is only time but will happen after we fix two issues regarding
sporadically killed forked JVM and then we would proceed with version 2.22.0
which will include only JUnit 5 Surefire provider but this cannot be done
tomorrow unfortunately.
> 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)
