[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342437#comment-342437
]
Jason van Zyl commented on MNG-5207:
------------------------------------
It's not just a matter of depMan, but what the definition of a dependency is in
the reactor. In 2.x the version was not taken into account and in 3.x it is
which is the source of the issue. I'm not saying what you're doing is wrong but
it is not necessarily correct because it works in 2.x. It is definitely not
typical to have multiple versions within the same reactor. You are the first
case I've personally seen.
> [Regression] Maven 3 fails to calculate proper build order with dependencies
> with classifiers
> ---------------------------------------------------------------------------------------------
>
> 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: Jason van Zyl
> Priority: Critical
> Fix For: Issues to be reviewed for 4.x
>
> Attachments: mng5207-it.tgz, mng-5207-minimal.tar.gz, 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 was sent by Atlassian JIRA
(v6.1.6#6162)
