[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150256#comment-17150256
]
Tibor Digana commented on SUREFIRE-1788:
----------------------------------------
[~kriegaex]
We have found a bug SUREFIRE-1809 where the plugin turns the CLI to JPMS style
even if you do not use {{module-info.java}} in the project. The workaround is
to use {{<useModulePath>false</useModulePath>}}.
Yes, the M4 and M5 changed for the JPMS projects. If M4 recognized that you
used {{src/main/java/module-info.java}}, the main artifacts were in module path
and test artifacts were in class path. The same is valid for M5. But if you
additionally use {{module-info.java}} in {{src/test/java}} then M5 would place
all dependencies to the module path except the surefire artifacts (still in
classpath).
> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
> Key: SUREFIRE-1788
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
> should be printed to INFO on the console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
