maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-4795) [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks
Date Sat, 04 Sep 2010 19:04:32 GMT

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

Benjamin Bentmann updated MNG-4795:
-----------------------------------

    Attachment: MNG-4795.zip

Running "mvn package" from the top-level of the attached project fails with a compilation
error in the (forked) sub module.

> [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
>         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

        

Mime
View raw message