[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258455#comment-16258455
]
Robert Scholte commented on SUREFIRE-1262:
------------------------------------------
Hi [~novanic], it seems like you underestimate the consequences of using open
source projects, the complexity of both surefire and Java9 and the available
resources that maintain this project. If this is a blocking issue, it would
have been great to step up and fix it together with us the first time you hit
it.
Though you can still help by verifying+confirming this issue is indeed fixed.
You can use the following snapshot repository:
https://repository.apache.org/content/groups/snapshots/
> 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)
