[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204728#comment-16204728 ]
Tibor Digana commented on SUREFIRE-1262: ---------------------------------------- [~rfscholte] I have finished refactoring [1] and the IT test {{ModulePathIT}} passed successfully. Let's wait for Jenkins build and then I can patch master with this change from the branch. https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=a72e152a7be7df06a379e92feafa6158bf1f1dab > 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 > Fix For: Backlog > > > 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 (v6.4.14#64029)