[
https://jira.codehaus.org/browse/MNG-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-5137:
-----------------------------------
Component/s: Reactor and workspace
> Reactor resolution does not work for forked multi module builds
> ---------------------------------------------------------------
>
> Key: MNG-5137
> URL: https://jira.codehaus.org/browse/MNG-5137
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.2.1, 3.0.3
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0.4
>
> Attachments: test.zip
>
>
> Running {{mvn clean package site}} on the attached multi-module test project
> fails with a dependency resolution issue. While the main build still builds
> the aggregator module, an aggregator (report) mojo forks the lifecycle and
> despite this forked lifecycle executing up to "package" phase, reactor
> resolution inside this forked lifecycle fails since the wrong project
> instances (those from the main build instead of the forked build) are
> searched for build output.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
