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

Gradle Community

`isTransitive = false` on the configuration or the dependency just gets you the dependency but no transitives

in the configuration it throws an exception

I found `archives` would probably do what I need but is not using variant selection (I mean, no attributes, it's legacy)

Really, `isTransitive = false` is what you are after

Or `transitive = false` if you are old-school (using Groovy DSL :smile:)

&gt; * What went wrong:
&gt; Could not determine the dependencies of task '::consumer:compileJava'.
&gt; &gt; Could not resolve all dependencies for configuration ':consumer:compileClasspath'.
&gt;    &gt; Cannot change dependencies of dependency configuration ':producer:api' after it has been included in dependency resolution.

that's for the code:
```
val jarOnly: Configuration by configurations.creating {
    isCanBeConsumed = false
    isCanBeResolved = true
    isTransitive=false
}

dependencies {
    jarOnly(project(":producer"))
    implementation(project(":producer"))
}```

Do you have an MCVE?
Doesn't sound like `isTransitive = false` should cause that

And no need for using String there if you have the configuration in a variable, then `jarOnly(...)` is available :slightly_smiling_face:

I'll try to make a reproducer, next week in working hours.

In the meantime the only "special" thing is that the code is in a convention plugins writen with kotlin-dsl

ok, I got something else, the dependencies block actually includes 2 times the producer subproject

```
dependencies {
    jarOnly(project(":produces:common")) {
        isTransitive = false
    }
    implementation(project(":produces:common"))
}```

and the failure is complaining about the :consumer:compileJava

Shouldn't be a problem.

Btw. do you still have the `isTransitive` on the configuration? Then having it on the dependency too ist just redundant. :smile:

It's really hard to guess what is going on.
I just know I used `isTransitive` on both, dependencies and configurations successfully in the past, so I can just guess that it is something else going wrong in your setup, but I cannot imagine what.

Or well, if you resolve that `jarOnly` at configuration time and after it is resolved you try to add something to `api` in producer, then I think you would get that error.

and found the culprit even if I don't understand the issue:
```tasks.withType&lt;Jar&gt;().configureEach {
        from(jarOnly.map { zipTree(it) })
    }```

I know it's related because commenting it out fixes the issue (obviously the jar is not as expected)

Add a breakpoint to both places, or some system out logging to verify the order.
Maybe something is eagerly configuring any of the `Jar` tasks.

Maybe it works better if you use an artifact transform to do the exploding instead of using `zipTree`.
That would also allow for the unzipped result to be reused if up to date.

good point, never used transforms before.

going to sleep now, but thanks a lot for your help, at lest I know how to proceed with the investigation