[GRADLE-3179] having multiple equal subproject names can cause StackOverFlow Created: 06/Oct/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.12
Fix Version/s: None

Type: Bug
Reporter: René Gröschke (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Having two projects with the same name in a multiproject build can cause Stackoverflow exception with the following stacktrace:

at java.util.TreeSet.iterator(TreeSet.java:181) 
at java.util.AbstractCollection.addAll(AbstractCollection.java:341) 
at org.gradle.api.internal.artifacts.DefaultResolvedDependency.getAllModuleArtifacts(DefaultResolvedDependency.java:87) 
at org.gradle.api.internal.artifacts.DefaultResolvedDependency.getAllModuleArtifacts(DefaultResolvedDependency.java:89)

I cannot fully reproduce the issue, but it seems related to the fact that both projects are configured to have the same GAV, though they are in different trees.

This might be a side effect of how we changed the resolution of projects with the same name.

Having a dependency section in project :features:foo like

dependencies {
	runtime project(":modules:foo")

causes the conflict resolution to kick in:

runtime - Partial runtime classpath provided by the hosting container.
+--- project :modules:foo -> project :features:foo (*)

Comment by Daz DeBoer [ 10/Feb/16 ]

Can someone confirm that this issue still exists in Gradle 2.11? Esin Yakub

Otherwise, without a way to reproduce this issue, I plan to close it.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:42:04 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.