[jira] Commented: (MAVEN-1751) "A cycle was detected" where no cycle can be found

[ 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 c

[jira] Commented: (MAVEN-1751) "A cycle was detected" where no cycle can be found

[ 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 > ---

[jira] Commented: (MAVEN-1751) "A cycle was detected" where no cycle can be found

[ 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 >

[jira] Commented: (MAVEN-1751) "A cycle was detected" where no cycle can be found

[ 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