"A cycle was detected" where no cycle can be found
--------------------------------------------------
Key: MAVEN-1751
URL: http://jira.codehaus.org/browse/MAVEN-1751
Project: Maven
Type: Bug
Versions: 1.1-beta-2
Environment: SUSE Linux 10.0 (kernel 2.6.13-15-smp), J2SDK 1.4.2_10
Reporter: Anders Heintz
Attachments: proj1_dependencies.xml, proj2_dependencies.xml,
proj3_dependencies.xml
I have a quite large multiproject project which I fail to build using Maven
1.1beta2 (Maven 1.0.2 works fine). I "divided and conquered" a bit and excluded
all but the most basic project, then added one at a time. When I included my
third project, the build fails with the message "A cycle was detected". The
dependencies for these tree projects (except external dependencies) are:
Project 1 depends on Project 2 and Project 3. Project 2 depends on Project 3.
Project 3 is a base "project" which contains common services and are used by
all other projects.
I'll attach the dependencies part of the three subprojects.
When I run the same goal (any multiproject goal, for example 'maven
-Dgoal=clean multiproject:goal') using Maven 1.0.2 it works fine:
Starting the reactor...
Our processing order:
webSelect Project 3
webSelect Project 2
webSelect Project 1
When I tried commenting out all dependencies apart from the project mentioned
above, it still fails, it even fails when I remove Project 1's dependency to
Project 3.
What is even more confusing is when I replace Project 1 with another subproject
which have the same dependencies it works fine (which however, is a ejb project
instead of being a jar project which Project 1 is).
--
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
