[SUREFIRE-1831] Module path is used without modules being declared by the project

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 3.0.0-M5
• Component/s: Maven Surefire Plugin
• Labels: jpms
• External issue URL: https://github.com/junit-team/junit5/issues/2377
• Assignee: Tibor Digana
• Reporter: Christian Stein
• Created: 11/Aug/20 13:20
• Updated: 13/Apr/21 15:10
• Resolved: 12/Aug/20 19:35

Description

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

Issue Links

• duplicates: SUREFIRE-1809 Differences between Oracle JDK and AdoptOpenJDK caused by JPMS
• links to: GitHub Pull Request #5352