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

Gradle Community

Does it make sense to add attributes to a `DependencyScopeConfiguration` ?

My understanding is that it’s meant to be extended from a resolvable or consumable configuration and the attributes are better set on those configurations?

Or is there a use case to set attributes on the `DependencyScopeConfiguration` directly?

I think so too, because you can add a dependency to a dependencyScope but resolve different artifacts using different attributes of different resolvable ones

Attributes from a dependencyScope and a resolvable? 

Yep. I’m expecting the attributes from the “resolvable” configuration to take precedence over the ones from the “dependency scope”?

I never tested it! But I guess, they are all added and attributes with the same name will be overwritten by the child one, the resolvable one. 

Put it otherwise, Is this valid?
```val dependencyScope = configurations.dependencyScope("dependencyScope") {
  attributes {
    attribute(Usage.USAGE_ATTRIBUTE, project.objects.named(Usage::class.java, Usage.SWIFT_API))
  }
}
val resolvable = configurations.resolvable("resolvable") {
  attributes {
    attribute(Usage.USAGE_ATTRIBUTE, project.objects.named(Usage::class.java, Usage.JAVA_API))
  }
  extendsFrom(dependencyScope.get())
}```

Maybe? Also, you should test moving extendsFrom to the top. 

top level?
```resolvable.get().extendsFrom(dependencyScope.get())```


No:
```val resolvable = configurations.resolvable("resolvable") {
  extendsFrom(dependencyScope.get())
  attributes {
    attribute(Usage.USAGE_ATTRIBUTE, project.objects.named(Usage::class.java, Usage.JAVA_API))
  }
}```

I would expect the order to be irrelevant there :thinking_face:

This is “declarative”, not imperative?

Maybe, I don't know, maybe it does make a difference because extendsFrom will be executed directly

Tests: <https://gist.github.com/martinbonnin/0e557827cb8938750fca6db3918cec2e>

Looks like the dependency scope attributes are not used

Also the order of `extendsFrom` doesn’t seem to matter (not shown in the gist but I did some manual testing)

If you add attributes to a regular Configuration that's configured to be a dependency-bucket, then you get a warning.

Does adding attributes to a `DependencyScopeConfiguration` trigger a warning somewhere? Maybe in a build scan?

Ah yes, it’s in the build scan: <https://scans.gradle.com/s/rw3fcnlomk2v4#deprecations>

Not in the console output though (at least not with `-i` )

Attributes on dependency scope configurations are indeed ignored

We should deprecate trying to add attributes to them

Created an issue <https://github.com/gradle/gradle/issues/30243> because I didn't find one (and there is no warning with 8.10)