You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/30 18:02:55 UTC

[jira] Updated: (MNG-3208) Injection of an inter-module dependency via profile does not affect reactor projects ordering

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

Jason van Zyl updated MNG-3208:
-------------------------------

    Fix Version/s:     (was: 3.x)
                   3.0-alpha-7

> Injection of an inter-module dependency via profile does not affect reactor projects ordering
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNG-3208
>                 URL: http://jira.codehaus.org/browse/MNG-3208
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Profiles, Reactor and workspace
>    Affects Versions: 3.0-alpha-1
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 3.0-alpha-7
>
>
> I don't know whether this is a problem in 2.0.7 (haven't had time to check yet), but when I inject a new inter-module dependency via profile it seems that the reactor build ordering is not affected. This is easy to reproduce:
> 1. Create a three-module reactor build:
> - first
> |
> |- second
> |- third
> 2. in a profile in 'second' put a dependency on 'third'
> 3. run the build without triggering the profile...the modules (listed in the above order) should build in that order
> 4. run the build with the profile activated...'third' SHOULD build ahead of 'second' now, but does not.
> I'll try to loop back and test this on 2.0.7 when I can.

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