[SUREFIRE-1993] Failsafe fails to detect module dependencies

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-M5
• Fix Version/s: 3.0.0-M6
• Component/s: Maven Failsafe Plugin
• Environment: Java 17 ; Maven 4.0.0-alpha-SNAPSHOT and 3.8.4
• Assignee: Maarten Mulders
• Reporter: Maarten Mulders
• Created: 28/Jan/22 16:44
• Updated: 27/Mar/22 23:53
• Resolved: 11/Feb/22 12:35

Description

Please see the attached project. It has three Maven modules, each defining its own JPMS module. The application module depends on an interface from the studentservice module, and the implementation for that interface lives in studentservice-provider. The module-info.java for the studentservice-provider module declares the implementation of that interface.

When you run the application using ./manually.sh, it correctly loads the studentservice-provider module. When you run the IT, it does not.

The application prints the module path to standard out.

From the test script it prints:

application/target/application-1.jar
studentservice/target/studentservice-1.jar
studentservice-provider/target/studentservice-provider-1.jar

From the integration test, which starts the same application, it prints:

application/target/application-1.jar
studentservice/target/studentservice-1.jar

 
Note how in the integration test the studentservice-provider is missing in the output.

Issue Links

• links to: GitHub Pull Request #463