[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365560#comment-365560 ] Jörg Schaible commented on MNG-5207: Now, that M221 is EOLed, what are our options? This is not an old project, where technology is freezed, we have to move forward also. @Stephen: You identified the location in code where the transitive deps where not considered. Can you give me a pointer? > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354279#comment-354279 ] Jörg Schaible edited comment on MNG-5207 at 10/13/14 4:44 AM: -- 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. bq. You are the first case I've personally seen. Maybe others did not recognize that the build produced stale results? was (Author: joehni): 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. b. You are the first case I've personally seen. Maybe others did not recognize that the build produced stale results? > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354279#comment-354279 ] Jörg Schaible edited comment on MNG-5207 at 10/13/14 4:43 AM: -- 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. b. You are the first case I've personally seen. Maybe others did not recognize that the build produced stale results? was (Author: joehni): 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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ 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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ 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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ 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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342004#comment-342004 ] Jason van Zyl commented on MNG-5207: This looks relatively easy to fix, Stephen seems to have a handle on it but the question is whether this is something that we actually want. While I'd admit what you're doing is ingenious I've never seen people use reactor different versions for the projects that are in the reactor and this is what is implicitly enforced. Not saying it's right or wrong right now, but that it works in 2.x where be basically have no formal specification is not in and of itself a compelling reason to restore. But it should either work or fail and tell you why. > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341804#comment-341804 ] Jörg Schaible commented on MNG-5207: Hi Stephen, bq. A rule of thumb to avoid this issue is that you should list leaf modules first and put modules with transitive dependencies last... Unfortunately it is no option to sort the modules if you deal with about Maven 400 projects nested multiple levels deep. We have some components there which provides services as EJB and their implementation will use other component's EJB clients. Maintaining the build order manually would be a nightmare. bq. Another solution is just to add the dependency of ejb to app and again the project sorter will sort correctly. This is even wrong, because your app should *not* contain the ejb nor their dependencies (those are implementation details), if those dependencies are not exposed through the EJB's API. Typically we declare the ejb-client dependency with a lot of exclusions. BTW: Thanks for investigation. M221 must have taken the transitive deps into account. IMHO this will also solve MNG-5472 > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341803#comment-341803
]
Stephen Connolly commented on MNG-5207:
---
FYI the workaround is to change
{code}
app
delegate
ejb
{code}
to
{code}
delegate
ejb
app
{code}
The project sorter will correctly pull ejb ahead of delegate and respects the
order in the modules unless direct dependencies indicate otherwise.
A rule of thumb to avoid this issue is that you should list leaf modules first
and put modules with transitive dependencies last...
Another solution is just to add the dependency of ejb to app and again the
project sorter will sort correctly.
I am currently investigating whether the project sorter is running prior to
dependency resolution. It may be acceptable to resolve ex-reactor dependencies
as early as the project sorter as if they are unavailable we will fail
anyway... though plugins such as shade could make them available later in the
reactor build... perhaps it is acceptable to just produce a best effort sorting
if ex-reactor dependencies are not available when sorting the projects
> [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341779#comment-341779 ] Stephen Connolly commented on MNG-5207: --- When adding the delegate vertex to the app node, as the delegate is 1-SNAPSHOT which is outside the reactor there is no edge added to the app node... we should be considering the transitive dependencies of app not just the immediate dependencies in constructing the graph. > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341778#comment-341778 ] Stephen Connolly commented on MNG-5207: --- So what I'm seeing when I step through with the debugger is that the app:2-SNAPSHOT vertex has no child nodes, hence it is first as it is the first and it has no dependencies... not sure why it doesn't have any children > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly updated MNG-5207: -- Attachment: mng-5207-minimal.tar.gz Minimal test case constructed from mng5207-it with a lot of the properties based cruft removed and the poms stripped back to the minimum. Confirmed that from a clean repo, passes with maven 2.2.1 and fails for maven 3.2.1 > [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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[
https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341576#comment-341576
]
Jörg Schaible commented on MNG-5207:
Hi Jason,
I have no permission to push, therefore here the diff:
{noformat}
$ git diff
diff --git a/build.sh b/build.sh
index 91be103..9e69a23 100755
--- a/build.sh
+++ b/build.sh
@@ -5,4 +5,4 @@ mvn -v
( cd prepare ; ./prepare.sh )
-mvn clean package
+mvn clean install
{noformat}
> [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.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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341503#comment-341503 ] Jason van Zyl commented on MNG-5207: I made a small repo with a script here: https://github.com/takari/MNG-5207 Clone the git repo and run ./build.sh, which displays the version of Maven, runs the prepare script and then executes Maven. If you can take a look and see what might be wrong because the build fails for me: https://gist.github.com/jvanzyl/9020379 > [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.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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340845#comment-340845 ] Jörg Schaible commented on MNG-5207: q. Is it expected to build correctly? For sure. If you had run the prepare step as explained above in the first comment. Or, didn't you simply use the attached integration test? > [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.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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5207: --- Fix Version/s: (was: 3.2) Issues to be reviewed for 4.x > [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.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)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340844#comment-340844 ] Jason van Zyl commented on MNG-5207: The right build order is calculated in 2.2.1 but the sample project still doesn't build. Is it expected to build correctly? > [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: 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5207: --- Assignee: Jason van Zyl (was: Kristian Rosenvold) > [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: 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5207: --- Summary: [Regression] Maven 3 fails to calculate proper build order with dependencies with classifiers (was: [Regression] Maven 3 fails to calculate proper build order) > [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: 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 was sent by Atlassian JIRA (v6.1.6#6162)
