[
http://jira.andromda.org/jira/browse/MAVEN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Plushnikov Michail closed MAVEN-69.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.4-SNAPSHOT
Assignee: Plushnikov Michail (was: Chad Brandon)
> Maven 2.1.0 gives cyclic reference error in module
> org.andromda.maven.plugins.site:andromda-doxia-module-xdoc
> -------------------------------------------------------------------------------------------------------------
>
> Key: MAVEN-69
> URL: http://jira.andromda.org/jira/browse/MAVEN-69
> Project: Maven Plugins
> Issue Type: Bug
> Components: APP
> Environment: AndroMDA 3.4-SNAPSHOT, maven 2.1.0, Sun JDK 1.5.0_09
> Reporter: Bob Fields
> Assignee: Plushnikov Michail
> Priority: Minor
> Fix For: 3.4-SNAPSHOT
>
>
> Running mvn install in directory maven\2\site\doxia gives the error:
> [INFO] The projects in the reactor contain a cyclic reference: Edge between
> 'Vertex{label='org.andromda.maven.plugins.site:andromda-doxia-module-xdoc'}'
> and
> 'Vertex{label='org.andromda.maven.plugins.site:andromda-doxia-module-xdoc'}'
> introduces to cycle in the graph
> org.andromda.maven.plugins.site:andromda-doxia-module-xdoc -->
> org.andromda.maven.plugins.site:andromda-doxia-module-xdoc
> Somehow the doxia module if causing a cycle within itself, normally there is
> a cycle between two different modules. Commenting out the doxia module
> project reference from maven\site\pom.xml allows all other modules to build
> correctly.
> The maven error isn't very helpful, must have been written by somebody from
> China or India. 'introduces to cycle'?
> Running maven in debug mode gives:
> [DEBUG] Adding managed dependencies for unknown:andromda-doxia-module-xdoc
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6
> [DEBUG] org.apache.maven:maven-archiver:jar:2.3
> [DEBUG] org.apache.maven.plugins:maven-resources-plugin:jar:2.2
> [DEBUG] commons-beanutils:commons-beanutils:jar:1.7.0
> [DEBUG] commons-collections:commons-collections:jar:3.2
> [DEBUG] commons-digester:commons-digester:jar:1.7
> [DEBUG] commons-io:commons-io:jar:1.4
> [DEBUG] commons-lang:commons-lang:jar:2.4
> [DEBUG] commons-logging:commons-logging:jar:1.1.1
> [DEBUG] commons-validator:commons-validator:jar:1.3.1
> [DEBUG] junit:junit:jar:3.8.2:test
> [DEBUG] log4j:log4j:jar:1.2.14
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> You can easily switch between maven 2.1.0 and any other version after 2.0.5
> just by renaming the file under maven\lib, the only difference is the one
> file maven-2.1.0-uber.jar.
> Running with 2.0.10 works perfectly fine. Dependency tree from that version
> shows:
> [INFO] [dependency:tree]
> [INFO]
> org.andromda.maven.plugins.site:andromda-doxia-module-xdoc:jar:3.4-SNAPSHOT
> [INFO] +- oro:oro:jar:2.0.7:compile
> [INFO] +- org.apache.maven.doxia:doxia-core:jar:1.0-alpha-8:compile
> [INFO] | +- org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-8:compile
> [INFO] | +- org.codehaus.plexus:plexus-utils:jar:1.0.4:compile
> [INFO] | \-
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> [INFO] | \- classworlds:classworlds:jar:1.1-alpha-2:runtime
> [INFO] +- commons-lang:commons-lang:jar:2.3:compile
> [INFO] \- org.apache.maven:maven-plugin-api:jar:2.0.4:compile
> Some maven site comments from others with a similar issue were resolved when
> duplicate project and dependency references were removed from the parent
> pom.xml, but that doesn't seem to be the case here. I'll try to post the
> error on the maven forums too. Anybody have any clue?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
