This message was deleted.

If you want the

bucketClasspath

from

consumer

to get the

bucketClasspath

from

producer

you need to declare attributes on the configurations so that Gradle picks the appropriate variant, otherwise it will take the default one, which likely will be

runtimeElements

. https://docs.gradle.org/current/userguide/variant_model.html

Looks a lot like you use the Kotlin plugin, right? That adds the "stdlib" by default. I am not sure where, but I won't be surprised if it adds it everywhere. I think there is an option to turn off that behavior in the Kotlin plugin.

ohhhh! it is probably KGP adding the stdlib to all configurations by default. My god how awful! (although... it also added the producer.jar...) @Thomas Broyer yes I am aware I need attributes. The question was why, without any attributes, I was getting dependencies anyway. I will experiment later with a Java project to see if I get this same weird behavior.

Kgp adds stdlib to compile classpath, but you are getting all transitive dependencies from

:producer:runtimeElements

I believe everything works as expected

no, I do want to add attributes. I'm simply trying to understand why, absent any, I got dependencies. Why would I get runtimeElements?

consumerbucket has a dependency on producerrubtimeElements (aka default)

why?

When you add any dependency, the resolution will find the best match given attributes, by default it will be

default

I see! thanks for clearing up the mystery. (a mystery to me anyway)

I'm looking at the docs (from my phone)

can you send me that doc link?

I would like to send you the link...but I haven't found it really (and to be true I'm not really focused on it)

I think the link is the one I posted earlier. (either that, or https://docs.gradle.org/current/userguide/cross_project_publications.html or https://docs.gradle.org/current/userguide/variant_attributes.html#sec:abm_algorithm, and also see upper in the page about the default values of some attributes, and compatibility and disambiguation rules)

this was the declaration

// consumer/build.gradle
dependencies {
  bucket project(':producer')
}

there's no obvious reason to me, looking at that, why it would ever get

runtimeElements

from

:producer

. The consumable configuration associated with the

bucket

configuration doesn't have any artifacts associated with it. In fact, I'm not actually sure how gradle gets from the dependency scope (

bucket

) to the consumable configuration (

bucketElements.extendsFrom(bucket)

)