[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338777#comment-338777
]
Jason van Zyl commented on MNG-5207:
------------------------------------
Jörg,
So you have project A, B, C, B and they are all at 1.0.0-SNAPSHOT, and in the
reactor together and you want to pull in, say, a different version of B -- that
is not 1.0.0-SNAPSHOT into the reactor to replace the version that is there?
Just want to make sure we're clear. And why do you do this? Just trying to
understand the use case as I don't know what is correct yet. Just because it
worked previously in 2.x doesn't mean we necessarily want to restore or
preserve that behaviour.
> [Regression] Maven 3 fails to calculate proper build order
> ----------------------------------------------------------
>
> Key: MNG-5207
> URL: https://jira.codehaus.org/browse/MNG-5207
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0.3
> Reporter: Jörg Schaible
> Assignee: Kristian Rosenvold
> Priority: Critical
> Fix For: 3.2
>
> Attachments: mng5207-it.tgz, MNG-5207.tgz
>
>
> Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in
> proper order, if a transitive dependency (that is part of the reactor build)
> is overruled in the dependencyManagement section with the current SNAPSHOT
> version. Build order is perfectly calculated with Maven 2.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
