This message was deleted.

Afair, attributes are but inherited, no. Just the declared dependencies.

If you reason in terms of configuration roles (https://docs.gradle.org/current/release-notes.html#configuration-role), there's no point declaring attributes on "dependency scope" configurations (aka dependency buckets). Attributes on "resolvable" configurations define how variants are selected when resolving that dependency, and attributes on "consumable" define what variant of this project it declares for others to consume. And "consumable" and "resolvable" configurations are leafs and only

extendsFrom

"dependency scope" configurations.

The last part is not mandatory though, is it? You should be able to extend one resolvable from another resolvable to resolve the same things just with different attributes. The attributes are just not inherited I think.

Yes it's not mandatory (might that change in the future?) There's not much point doing so though as you won't be able to add dependencies to consumable or resolvable configurations, so nothing would be inherited except for the list of configurations they extend from (this might be a good reason to extend from a resolvable configurations, e.g. only to change the attributes, or possibly combine it with another configuration –that one sounds weird though).

e.g. only to change the attributes

Exactly, that's the use-case here 🙂