[
https://issues.apache.org/jira/browse/SUREFIRE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489305#comment-17489305
]
Maarten Mulders commented on SUREFIRE-1993:
-------------------------------------------
Thanks, running {{install}} rather than {{verify}} did the trick. Expect a PR
soonish™.
> Failsafe fails to detect module dependencies
> --------------------------------------------
>
> Key: SUREFIRE-1993
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1993
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 3.0.0-M5
> Environment: Java 17
> Maven 4.0.0-alpha-SNAPSHOT and 3.8.4
> Reporter: Maarten Mulders
> Assignee: Maarten Mulders
> Priority: Minor
> Fix For: 3.0.0-M6
>
> Attachments: reproducer.zip
>
>
> 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:
> {code:java}
> application/target/application-1.jar
> studentservice/target/studentservice-1.jar
> studentservice-provider/target/studentservice-provider-1.jar{code}
> From the integration test, which starts the same application, it prints:
> {code:java}
> application/target/application-1.jar
> studentservice/target/studentservice-1.jar{code}
>
> Note how in the integration test the *studentservice-provider* is missing in
> the output.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
