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

Non-modules are put on the module path when test sources contain a module-info file

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0-M5
    • Fix Version/s: None
    • Component/s: process forking
    • Labels:
      None

      Description

      When the test sources contain a module-info file, Surefire currently puts everything on the module path, even dependencies that are not modules.
      When the main sources contain a module-info file, it uses Plexus-Java to determine what to put on the module path and what to put on the classpath.

      I'm not sure what kind of use cases this will break, but it seems inconsistent to me. Shouldn't Plexus-Java be used in both cases? Marking as a minor issue since I'm not blocked by this, I was just curious why this was done differently.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              oehme Stefan Oehme
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: