[ https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090562#comment-17090562 ]
Tibor Digana commented on SUREFIRE-1262: ---------------------------------------- [~Pavel_K] Did you see the dump files in {{com.foo.plugin\target\surefire-reports\}}? Many users don't read the console error log: {noformat} [ERROR] Please refer to C:\vcs\github\surefire-jpms\com.foo.plugin\target\surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. {noformat} The dump files are produced by the JVM, saying: Error occurred during initialization of boot layer java.lang.module.FindException: Module *java.xml.bind* not found, required by com.foo.api It looks like we are missing the JAXB library. > 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)