[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420283#comment-15420283
]
Robert Scholte commented on SUREFIRE-1262:
------------------------------------------
Forked VM would already be a good start, so maybe this issue should be splitted
into 2 improvements. I'm not sure it there's a solution or the
IsolatedClassloader. If it is possible, we probably need to use a
[Layer|http://cr.openjdk.java.net/~mr/jigsaw/spec/api/java/lang/reflect/Layer.html].
There's an example on the javadoc page. #defineModulesWithOneLoader won't work
because of the package overlap, but #defineModulesWithManyLoaders seems fine.
It is probably a matter trying several options and having contact with the
Jigsaw team. I can help you with the latter.
> Add modulepath support
> ----------------------
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Robert Scholte
>
> 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 {{-Xpatch target/test-classes}}
> which makes it possible to use the same packages as target/classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
