You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Heintz (JIRA)" <ji...@codehaus.org> on 2006/03/13 10:26:30 UTC
[jira] Created: (MAVEN-1751) "A cycle was detected" where no cycle
can be found
"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
[jira] Commented: (MAVEN-1751) "A cycle was detected" where no
cycle can be found
Posted by "Anders Heintz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=comments#action_60858 ]
Anders Heintz commented on MAVEN-1751:
--------------------------------------
Thanks for your information, let me know if I can be of any help with testing etc.
> "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
[jira] Closed: (MAVEN-1751) "A cycle was detected" where no cycle
can be found
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=all ]
Lukas Theussl closed MAVEN-1751.
--------------------------------
Assignee: Lukas Theussl
Resolution: Cannot Reproduce
> "A cycle was detected" where no cycle can be found
> --------------------------------------------------
>
> Key: MAVEN-1751
> URL: http://jira.codehaus.org/browse/MAVEN-1751
> Project: Maven
> Issue Type: Bug
> Affects Versions: 1.1-beta-2
> Environment: SUSE Linux 10.0 (kernel 2.6.13-15-smp), J2SDK 1.4.2_10
> Reporter: Anders Heintz
> Assigned To: Lukas Theussl
> Fix For: 1.1-beta-3
>
> Attachments: MAVEN-1751.zip, 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
[jira] Updated: (MAVEN-1751) "A cycle was detected" where no cycle
can be found
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=all ]
Lukas Theussl updated MAVEN-1751:
---------------------------------
Attachment: MAVEN-1751.zip
Attached a simple test project for the scenario you describe. I cannot reproduce the bug (neither with m1.1-beta-2), please check.
> "A cycle was detected" where no cycle can be found
> --------------------------------------------------
>
> Key: MAVEN-1751
> URL: http://jira.codehaus.org/browse/MAVEN-1751
> Project: Maven
> Issue Type: Bug
> Affects Versions: 1.1-beta-2
> Environment: SUSE Linux 10.0 (kernel 2.6.13-15-smp), J2SDK 1.4.2_10
> Reporter: Anders Heintz
> Fix For: 1.1-beta-3
>
> Attachments: MAVEN-1751.zip, 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
[jira] Commented: (MAVEN-1751) "A cycle was detected" where no
cycle can be found
Posted by "David Jencks (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=comments#action_60908 ]
David Jencks commented on MAVEN-1751:
-------------------------------------
I don't know if it is related to this exact problem, but I have noticed that if I accidentally have 2 subprojects with the same name, maven claims there is a cycle. Changing the name of one project allows the build to proceed.
> "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
[jira] Updated: (MAVEN-1751) "A cycle was detected" where no cycle
can be found
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=all ]
Arnaud Heritier updated MAVEN-1751:
-----------------------------------
Fix Version: 1.1-beta-3
> "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
> Fix For: 1.1-beta-3
> 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
[jira] Commented: (MAVEN-1751) "A cycle was detected" where no
cycle can be found
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=comments#action_60862 ]
Arnaud Heritier commented on MAVEN-1751:
----------------------------------------
Thanks, I'll deploy a snapshot to allow you to test it ASAP.
> "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
[jira] Commented: (MAVEN-1751) "A cycle was detected" where no
cycle can be found
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1751?page=comments#action_60853 ]
Arnaud Heritier commented on MAVEN-1751:
----------------------------------------
It's certainly related to MAVEN-1750.
We have several problems with multiprojects : MAVEN-1741, MAVEN-1710, MAVEN-1691, ...
It's on the top of my todo list
> "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