You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2011/07/27 12:41:42 UTC

[jira] Closed: (MNG-5137) Reactor resolution does not work for forked multi module builds

     [ https://jira.codehaus.org/browse/MNG-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-5137.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.4
         Assignee: Benjamin Bentmann

Fixed in [r1151421|http://svn.apache.org/viewvc?view=revision&revision=1151421].

> 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