Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.9, 2.1.0-M1, 3.0-alpha-1
-
Fix Version/s: 3.0-alpha-3
-
Component/s: Reactor and workspace
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
Just to officially track the reason why the parent POM maven-plugins currently excludes the maven-project-info-reports-plugin from the reactor:
[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
It appears the ProjectSorter does not take versions into account, i.e. there is no cycle in a multi-module scenario like this:
parent:1 - plugin-a:2.0 which uses plugin-b:1.0 - plugin-b:2.0 which uses plugin-a:1.0
Issue Links
- relates to
-
MNG-4854
[regression] ProjectSorter neglects conflicted versions
-
-
MNG-4890
-pl, -am and -amd options don't consider the version of the artefacts for building the reactor
-
-
MSHARED-165
Mediate dependency versions for stricter Maven3 ProjectSorter
-
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