[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258431#comment-16258431
]
Sven Strohschein commented on SUREFIRE-1262:
--------------------------------------------
Hi,
could you please tell me when the fix / version 2.21.0 will be released or
where can I find a nightly/snapshot version? At the moment no Maven project can
use Java 9 services ("provides ... with ..." within the module-info file),
because the module-path has to be used instead of the class-path, so tests are
not finding/loading the service implementations... and there seem to be no
alternative to surefire. I had expected this is ready before the release of
Java 9 (early access versions were a long time ago available).
> 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)
