[
https://jira.codehaus.org/browse/MNG-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5078.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Assignee: Benjamin Bentmann
> Dependency on pom-project not resolved in reactor on multi-module build
> -----------------------------------------------------------------------
>
> Key: MNG-5078
> URL: https://jira.codehaus.org/browse/MNG-5078
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Ryan J
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
> Attachments: pom-dep-problem.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
