You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2016/08/14 09:18:22 UTC

[jira] [Commented] (SUREFIRE-1262) Add modulepath support

    [ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420274#comment-15420274 ] 

Tibor Digana commented on SUREFIRE-1262:
----------------------------------------

[~rfscholte]
{{-Xpatch target/test-classes}} would be for the forked VM. What to change in IsolatedCL in case the tests run in Maven process?

> 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)