[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342007#comment-342007
]
Jörg Schaible commented on MNG-5207:
------------------------------------
For me it is a simple consequence using dependencyManagement for transitive
deps. If you're allowed to overwrite/manage a transitive dep with a SNAPSHOT
version, then Maven should also recognize that it is part of the current
reactor build and adjust the build sequence accordingly, because it *requires*
the SNAPSHOT at some point. If you have cleaned your local repo before, the
build simply breaks if the build order does not respect this dependency.
Currently Maven is simply not aware at all stages what it tries to build.
> [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)
