You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pavel_K (Jira)" <ji...@apache.org> on 2020/04/22 15:12:00 UTC
[jira] [Issue Comment Deleted] (SUREFIRE-1262) Add modulepath
support
[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel_K updated SUREFIRE-1262:
------------------------------
Comment: was deleted
(was: [~rfscholte] Thank you very much for your help. However, moving in that direction I got several questions which I posted on SO here https://stackoverflow.com/questions/61368033/mixing-classpath-and-module-path-in-maven-surefire-plugin )
> 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
(v8.3.4#803005)