Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5078

Dependency on pom-project not resolved in reactor on multi-module build

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 3.0-alpha-3
    • Component/s: None
    • Labels:
      None

      Description

      I'm running into the issue described in the following thread:

      http://maven.40175.n5.nabble.com/Dependency-on-pom-project-not-resolved-in-reactor-on-multi-module-build-td3309198.html

      I can't find a similar bug report, so I'm guessing one was never submitted. The original poster included a sample project. I'll attach it here. To reproduce the issue, run 'mvn package' on the attached project. I would expect the POM dependency for module A to get resolved as part of the reactor, but it does not.

      This can cause unexpected behavior for any multi-module projects that rely on dependency grouping modules as described here:

      http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html

      Rather than getting dependency information from the current reactor, a stale POM from the local (or remote) repository is used. If no POM has ever been installed, the build fails instead.

        Attachments

        1. pom-dep-problem.zip
          2 kB
          Ryan J

          Issue Links

            Activity

              People

              • Assignee:
                bentmann Benjamin Bentmann
                Reporter:
                jptech Ryan J
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: