[
https://issues.apache.org/jira/browse/SUREFIRE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1831.
----------------------------------
Assignee: Tibor Digana
Resolution: Duplicate
> Module path is used without modules being declared by the project
> -----------------------------------------------------------------
>
> Key: SUREFIRE-1831
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1831
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Christian Stein
> Assignee: Tibor Digana
> Priority: Critical
> Labels: jpms
>
> [https://github.com/junit-team/junit5/issues/2377]
> @rmannibucau analyzed the underlying issue. It's within SF/FS usage of a
> feature Plexus, namely
> `org.codehaus.plexus.languages.java.jpms.LocationManager#resolvePath(java.nio.file.Path,
> org.codehaus.plexus.languages.java.jpms.ModuleNameExtractor)`.
> > this impl resolves the jpms name even from automatic name or even jar file
> > name
> > then surefire uses the fact there is a name to know if it is a jpms module
> > actually you never know upfront if a jar is used as a jpms module or not
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
