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 2010/09/11 22:21:33 UTC

[jira] Closed: (MNG-4795) [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks

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

Benjamin Bentmann closed MNG-4795.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-beta-4
         Assignee: Benjamin Bentmann

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

> [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4795
>                 URL: http://jira.codehaus.org/browse/MNG-4795
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-beta-2
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-beta-4
>
>         Attachments: MNG-4795.zip
>
>
> Currently, dependency resolution happens only at the beginning of a project build and then only for the current project. This means if the current project happens to bind an aggregator into its lifecycle which forks the lifecycle in a reactor build, any forked project not previously built during the main build will have its dependencies unresolved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira