[SUREFIRE-1809] Differences between Oracle JDK and AdoptOpenJDK caused by JPMS

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M5
• Fix Version/s: 3.0.0-M6
• Component/s: Maven Failsafe Plugin, Maven Surefire Plugin
• Assignee: Tibor Digana
• Reporter: Jiri Ondrusek
• Created: 25/Jun/20 11:43
• Updated: 17/Aug/20 11:28
• Resolved: 08/Jul/20 12:06

Description

I was upgrading maven-surefire-plugin to 3.0.0-M5 in [camel-quarkus|https://github.com/apache/camel-quarkus] project. Unfortunately there was a test which was failing on CI (using AdoptOpenJDK build 11.0.7+10) and there was no failure on my local machine (using Oracle "11.0.7" 2020-04-14 LTS).
Problem was caused by JPMS. On Orace JDK this was turned off by default. On AdoptOpenJDK it was turned on by default. Solution was to turn this feature off by configuration (https://github.com/apache/camel-quarkus/pull/1383).

It would be nice if default behavior was the same for different Java vendors.

Difference seems to be coming from this line - https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L1423
On AdoptOpenJDK both 3 clausules are true. On Oracle JDK the last one is false.

Issue Links

• is duplicated by: SUREFIRE-1831 Module path is used without modules being declared by the project
• is duplicated by: SUREFIRE-1833 Classes of dependency not found since 3.0.0-M5