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

Gradle Community

when using a gradle dep scan (online) i can see that the `other-library` is part of the compile and runtime classpath (via library-a)

Yes, `implementation` means it is on the compile and runtime classpath of `library-a` and on the runtime classpath of your project

If that is not the case, either something is misconfigured or you found a bug, but tbh I would wonder if it is a bug that is not yet found. Maybe you can knit an MCVE?

thank you for the answers already! So as expected, the 'app' project (spring boot project) that includes `library-a` does itself not need to include `other-library` in its `implementation`  dependencies - it should be included, also for runtime.

Of course. Would be ridiculous if you were forced to redeclare all transitive dependencies.

Besides that you would use `runtimeOnly` unless you reference code from those dependencies in your own code.

But if so, you would declare it, even if it comes in transitively already

Just to be sure doesnt `implementation` mean, it is only on the runtime classpath on the app? so assuming is have

```dependencies {
  implementation library-a;
}```
in the app

an library-a defined
```dependencies {
  implementation other-library
}```
then other-library will only be on the runtime-classpath off `app`, right?

does the behavior change when i `includeBuild` the project instead of consuming it via the nexus? it seems so

While the project substitution works well for the compile and runtime classpath , it does not work / is not applied to the testCompileClassPath nor testRuntimeClassPath

this means, that running our spring boot tests, the outdated nexus based jar was used, while when looking at the compile/runtime classpath, we could see the proper substitution and all the dependencies

Unless I misunderstood what you mean, it should work fine.
Can you maybe knit an MCVE?
That will also help if you report it as issue.

sorry a reproducer is not just a 5 minutes kind of work - at least for now i would go down that route yet. I can report the issue myself i guess, no problem, fairly sure this is an issue with gradle or 'managing expectations'

You need to report yourself either way if you want it reported.
I'm just a user like you, I'm not going to be your secretary. :wink:

sorry was not sure you are a core developer. Was not implying it anyway