Multiple buildSrc in different composite builds breaks the IntelliJ IDEA import

[GFriedrich]

When having a root project with two included composite build projects and each of these projects uses a "buildSrc" folder, the import of the main project via IntelliJ IDEA fails.

Expected Behavior

The import/sync should run without an issue.

Current Behavior

The import/sync of the Gradle project fails.

Steps to Reproduce

Have a project A including two other composite build projects B and C.
B and C should have a buildSrc folder.
Importing/running sync in IntelliJ IDEA fails due to:

Caused by: java.lang.IllegalArgumentException: Duplicate root element buildSrc
	at org.gradle.plugins.ide.internal.configurer.HierarchicalElementDeduplicator$StatefulDeduplicator.deduplicate(HierarchicalElementDeduplicator.java:122)
	at org.gradle.plugins.ide.internal.configurer.HierarchicalElementDeduplicator$StatefulDeduplicator.calculateNewNames(HierarchicalElementDeduplicator.java:102)
	at org.gradle.plugins.ide.internal.configurer.HierarchicalElementDeduplicator$StatefulDeduplicator.getNewNames(HierarchicalElementDeduplicator.java:89)
	at org.gradle.plugins.ide.internal.configurer.HierarchicalElementDeduplicator$StatefulDeduplicator.access$100(HierarchicalElementDeduplicator.java:73)
	at org.gradle.plugins.ide.internal.configurer.HierarchicalElementDeduplicator.deduplicate(HierarchicalElementDeduplicator.java:67)
	at org.gradle.plugins.ide.internal.configurer.DefaultUniqueProjectNameProvider.getDeduplicatedNames(DefaultUniqueProjectNameProvider.java:44)
	at org.gradle.plugins.ide.internal.configurer.DefaultUniqueProjectNameProvider.getUniqueName(DefaultUniqueProjectNameProvider.java:34)
	at org.gradle.plugins.ide.idea.IdeaPlugin.configureIdeaModule(IdeaPlugin.java:265)
	at org.gradle.plugins.ide.idea.IdeaPlugin.onApply(IdeaPlugin.java:136)

As far as I can see, during the import/sync the IDEA plugin of Gradle gets included to all builds to gather the Gradle model for projects. But obviously the plugin can't handle multiple buildSrc folders.

Your Environment

Gradle 5.3.1

[GFriedrich]

Oh great - I've found a workaroud:
Placing a settings.gradle file within the buildSrc folder to overwrite the rootProject.name fixes the issue. Hopefully this doesn't end up in new issues elsewhere. 😉

[big-guy]

@GFriedrich do you know if this used to work with an earlier version of Gradle or IDEA?

[GFriedrich]

@big-guy: No, otherwise I would have created a regression issue.

[JojOatXGME]

I could not reproduce it on Windows but a colleague had the same problem on Mac. I'm just wondering if the bug might be platform dependent. However, it would seem suspect to me if this behavior depends on the operating system. Anyway, did you encounter the issue on Windows or on another operating system?

[GFriedrich]

I've experienced the issue on Windows and Linux.

[JojOatXGME]

There was some leftover of a buildSrc on the Mac. After deleting it, the problem did not occur anymore. Interestingly, there are still multiple other buildSrc directories within the composite build which do not cause the problem.

[wayonEmes]

Oh great - I've found a workaroud:
Placing a settings.gradle file within the buildSrc folder to overwrite the rootProject.name fixes the issue. Hopefully this doesn't end up in new issues elsewhere. 😉

thanks . I don't know why, but it works.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[GFriedrich]

Just checked and at least with latest IntelliJ IDEA 2020.2.3 and Gradle 6.5.1 (or higher) this is not happening anylonger.
Therefore I'm closing the ticket...