maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1262) Add modulepath support
Date Fri, 02 Nov 2018 05:13:00 GMT

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

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

[~aaime]
[~rfscholte]
Maybe this helps:
[ModularClasspathForkConfiguration.java|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ModularClasspathForkConfiguration.java]


The forked JVM does not start via MANIFEST.MF in booter Jar. Instead it starts surefire args
file with Jigsaw attributes in TEMP. Is it this you want to have described in documentation?

> 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
>            Priority: Major
>             Fix For: 2.21.0
>
>
> 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
(v7.6.3#76005)

Mime
View raw message