Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-1993

Failsafe fails to detect module dependencies

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.0.0-M5
    • 3.0.0-M6
    • Maven Failsafe Plugin
    • None
    • Java 17
      Maven 4.0.0-alpha-SNAPSHOT and 3.8.4

    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.

      Attachments

        1. reproducer.zip
          19 kB
          Maarten Mulders

        Issue Links

          Activity

            People

              mthmulders Maarten Mulders
              mthmulders Maarten Mulders
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: