Maven 2 & 3

cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1.0
  • Fix Version/s: 2.2.0
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

With a CXF trunk checkout (http://svn.apache.org/repos/asf/cxf/trunk/), if you run:

mvn -Pfastinstall (to get the required plugins and such installed)
and then
mvn -Psetup.eclipse

to setup the eclipse stuff, that works fine with mvn 2.0.[8-10], but with 2.1.0-RC1, I get:
[INFO] The projects in the reactor contain a cyclic reference: Edge between 'Vertex{label='org.apache.cxf:cxf'}' and 'Vertex{label='org.apache.cxf:cxf-buildtools'}' introduces to cycle in the graph org.apache.cxf:cxf-buildtools --> org.apache.cxf:cxf --> org.apache.cxf:cxf-buildtools

Issue Links

This issue is related to:
MNG-2668 Plugin dependencies should be considered when the reactor creates the build order list Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

Likely related to MNG-2668: org.apache.cxf:cxf declares an execution of the maven-antrun-plugin, using org.apache.cxf:cxf-buildtools as a plugin dependency. And org.apache.cxf:cxf-buildtools inherits from org.apache.cxf:cxf...

Show
Benjamin Bentmann added a comment - Likely related to MNG-2668: org.apache.cxf:cxf declares an execution of the maven-antrun-plugin, using org.apache.cxf:cxf-buildtools as a plugin dependency. And org.apache.cxf:cxf-buildtools inherits from org.apache.cxf:cxf...
Hide
Permalink
Dan Diephouse added a comment -

I'm still experiencing this with 2.1.0 final with various projects (Mule, Mule Galaxy...). Was this really addressed in 2.1.0? You can check out our sources here: https://svn.muleforge.org/galaxy/trunk

Show
Dan Diephouse added a comment - I'm still experiencing this with 2.1.0 final with various projects (Mule, Mule Galaxy...). Was this really addressed in 2.1.0? You can check out our sources here: https://svn.muleforge.org/galaxy/trunk
Hide
Permalink
John Casey added a comment -

I mean, the fairies promised they'd take care of it...

The problem in CXF was between a plugin dependency that was in the modules list, whose parent added the dependency to the plugin. Maybe mule's situation is slightly different.

Show
John Casey added a comment - I mean, the fairies promised they'd take care of it... The problem in CXF was between a plugin dependency that was in the modules list, whose parent added the dependency to the plugin. Maybe mule's situation is slightly different.
Hide
Permalink
John Casey added a comment -

The problem in the Muleforge stuff is that the checkstyle plugin is listed in the main build/plugins section, not in pluginManagement. This is probably because (IIRC) reporting plugins don't make use of pluginManagement for versioning/dependencies/etc. which forces the user to list them in the main build/plugins section. At any rate, the build tools were listed in the parent pom in this way, and since the build tools POM inherits from this parent, it meant that the build tools project build looked like it relied on the checkstyle plugin and its build tools dependency...and a single-node cycle resulted.

I'm putting in an exception for a project referencing itself from plugin-level dependencies, with the understanding that if this plugin were actually used in the dependency project's build it would either:

A. use an older copy of the project currently being built, in order to build the project...ICK
B. result in an ArtifactNotFoundException

Show
John Casey added a comment - The problem in the Muleforge stuff is that the checkstyle plugin is listed in the main build/plugins section, not in pluginManagement. This is probably because (IIRC) reporting plugins don't make use of pluginManagement for versioning/dependencies/etc. which forces the user to list them in the main build/plugins section. At any rate, the build tools were listed in the parent pom in this way, and since the build tools POM inherits from this parent, it meant that the build tools project build looked like it relied on the checkstyle plugin and its build tools dependency...and a single-node cycle resulted. I'm putting in an exception for a project referencing itself from plugin-level dependencies, with the understanding that if this plugin were actually used in the dependency project's build it would either: A. use an older copy of the project currently being built, in order to build the project...ICK B. result in an ArtifactNotFoundException

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.