[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090783#comment-17090783
]
Pavel_K commented on SUREFIRE-1262:
-----------------------------------
[~rfscholte] I wouldn't advice to put all modules on module-path as there are a
lot of libraries that don't work well there. Put only those that are required
in module-info of the module that is being tested and in module-info of its
dependencies.
Let's think this way - on module path we put only those jar that either have
module-info or are required in module-info (so some module is going to use it
as automatic module).
For example, foo.jar has module-info and requires bar.jar. Bar.jar doesn't have
module-info and it uses baz.jar. Baz.jar doesn't have module-info. So, foo.jar
(explicit module), bar.jar (automatic module) are on module-path, baz is on
class-path (unnamed module).
> 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)
