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

dependenciesToScan Does Not Leverage Classpath Elements

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.20
    • Fix Version/s: 2.22.0
    • Component/s: Maven Surefire Plugin
    • Labels:
      None

      Description

      The <dependenciesToScan> configuration attribute relies solely on installed artifacts. This is an issue when the targeted dependencies were built as part of the current session. The net result is that stale artifacts are used (i.e. if the dependency has changed since it was last installed) or the tests are not executed at all (if the dependency has not been previously installed.

      Attached is a sample project that illustrates this issue:

      Given I have a multi-module project
      And the first module built includes test classes as part of the project artifact
      And subsequent modules scan the first for unit tests to execute
      When I execute the test goal (prior to any install)
      Then the build should succeed
      And tests should be executed with each module

        Attachments

          Activity

            People

            • Assignee:
              tibor17 Tibor Digana
              Reporter:
              owen.farrell Owen Farrell
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Time Spent - 48h Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - 48h Remaining Estimate - 24h
                48h