[jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions
[
http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233744#action_233744
]
Julien HENRY commented on MNG-3814:
---
If this is fixed maybe could you revert changes done in aggregator POM
maven-plugins.
Reactor builds fail due to erroneous cycle in project sorting which does not
consider versions
--
Key: MNG-3814
URL: http://jira.codehaus.org/browse/MNG-3814
Project: Maven 2 3
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Fix For: 3.0-alpha-3
Just to officially track the reason why the parent POM {{maven-plugins}}
currently excludes the maven-project-info-reports-plugin from the reactor:
{noformat}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference:
Edge between
'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
and
'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
introduces to cycle in the graph
org.apache.maven.plugins:maven-project-info-reports-plugin --
org.apache.maven.plugins:maven-remote-resources-plugin --
org.apache.maven.plugins:maven-project-info-reports-plugin
{noformat}
It appears the {{ProjectSorter}} does not take versions into account, i.e.
there is no cycle in a multi-module scenario like this:
{noformat}
parent:1
- plugin-a:2.0 which uses plugin-b:1.0
- plugin-b:2.0 which uses plugin-a:1.0
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions
[
http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233745#action_233745
]
Benjamin Bentmann commented on MNG-3814:
It's fixed only in M3 and the aggregator POM already has a profile for M3 that
enables all modules.
Reactor builds fail due to erroneous cycle in project sorting which does not
consider versions
--
Key: MNG-3814
URL: http://jira.codehaus.org/browse/MNG-3814
Project: Maven 2 3
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Fix For: 3.0-alpha-3
Just to officially track the reason why the parent POM {{maven-plugins}}
currently excludes the maven-project-info-reports-plugin from the reactor:
{noformat}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference:
Edge between
'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
and
'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
introduces to cycle in the graph
org.apache.maven.plugins:maven-project-info-reports-plugin --
org.apache.maven.plugins:maven-remote-resources-plugin --
org.apache.maven.plugins:maven-project-info-reports-plugin
{noformat}
It appears the {{ProjectSorter}} does not take versions into account, i.e.
there is no cycle in a multi-module scenario like this:
{noformat}
parent:1
- plugin-a:2.0 which uses plugin-b:1.0
- plugin-b:2.0 which uses plugin-a:1.0
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions
[
http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155844#action_155844
]
Régis Décamps commented on MNG-3814:
The problem occurs with any type of dependency. It can be a plugin dependency
or a dependency.
My project fails because
module-1.1 (uses plugin)- plugin-1.0 (which depends on)- module-1.0
Reactor builds fail due to erroneous cycle in project sorting which does not
consider versions
--
Key: MNG-3814
URL: http://jira.codehaus.org/browse/MNG-3814
Project: Maven 2
Issue Type: Bug
Components: Reactor and workspace
Affects Versions: 2.0.9, 2.1.0-M1, 3.0-alpha-1
Reporter: Benjamin Bentmann
Just to officially track the reason why the parent POM {{maven-plugins}}
currently excludes the maven-project-info-reports-plugin from the reactor:
{noformat}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference:
Edge between
'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
and
'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
introduces to cycle in the graph
org.apache.maven.plugins:maven-project-info-reports-plugin --
org.apache.maven.plugins:maven-remote-resources-plugin --
org.apache.maven.plugins:maven-project-info-reports-plugin
{noformat}
It appears the {{ProjectSorter}} does not take versions into account, i.e.
there is no cycle in a multi-module scenario like this:
{noformat}
parent:1
- plugin-a:2.0 which uses plugin-b:1.0
- plugin-b:2.0 which uses plugin-a:1.0
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
