Stefan Oehme created SUREFIRE-1902:
--------------------------------------
Summary: Non-modules are put on the module path when test sources
contain a module-info file
Key: SUREFIRE-1902
URL: https://issues.apache.org/jira/browse/SUREFIRE-1902
Project: Maven Surefire
Issue Type: Bug
Components: process forking
Affects Versions: 3.0.0-M5
Reporter: Stefan Oehme
When the test sources contain a module-info file, Surefire currently [puts
everything on the module
path|https://github.com/apache/maven-surefire/blob/b9b2381a3dba6574bb69bd91d45fe0edea29c779/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L2057],
even dependencies that are not modules.
When the main sources contain a module-info file, it [uses
Plexus-Java|https://github.com/apache/maven-surefire/blob/b9b2381a3dba6574bb69bd91d45fe0edea29c779/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L2034]
to determine what to put on the module path and what to put on the classpath.
I'm not sure what kind of use cases this will break, but it seems inconsistent
to me. Shouldn't Plexus-Java be used in both cases? Marking as a minor issue
since I'm not blocked by this, I was just curious why this was done differently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
