[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers

["Jörg Schaible (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354279#comment-354279 ] 

Jörg Schaible commented on MNG-5207:
------------------------------------

So what would you do maintaining a release of ~400 artifacts with own release cycle? E.g. if we fix a NPE in an artifact A with utility stuff used by ~50% of the released stuff, we simply create a branch for A and branches for the artifacts that deliver aggregations of other artifacts (war, ear, zip). That way we have in the end ~10 releases in the branch. Otherwise we would have to perform ~200 unnecessary releases, although the artifacts compiling against A will not change at all. 

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