[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090055#comment-17090055 ]
Pavel_K commented on SUREFIRE-1262: ----------------------------------- [~tibordigana] I found out why I added forkCount. Here is almost empty project. Please, do the following: git clone https://github.com/PashaTurok/surefire-jpms.git, mvn clean install. I added forkCount=0 because it doesn't work without it, however, when I add forkCount=0 I can't use module path. > 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)