From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Is there an official best practice around setting attributes on configurations? I am seeing a lot of configurations in the ecosystem which get created with no attributes which causes ambiguity errors during variant selection

No, nothing official
<https://github.com/gradle/gradle/issues/36934>

Screenshot 2026-08-28 at 00.18.23.png

Even GitHub doesn't want to look at that issue :see_no_evil:

The whole thing is super fragile IMO. It's really hard to get predictable results because of all the inputs that go into the algorithm

And yea the lack of strict recommendation do not help

There is this as a community guide: <https://github.com/liutikas/gmm-wiki|github.com/liutikas/gmm-wiki>

Also, you set attributes on resolvable and consumable configurations only. Setting attributes on a dependency scope configuration have no effect but “Gradle does not warn you”. 

One such best practice has been added to the 9.7.0 docs: <https://docs.gradle.org/current/userguide/best_practices_dependencies.html#use_attributes_on_configurations|docs.gradle.org/current/userguide/best_practices_dependencies.html#…>