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

Gradle Community

this works when B has `api(lib)`but not with `implementation(lib)`

```configurations.compileClasspath {
    resolutionStrategy {
        eachDependency {
            if (requested.group == "io.ktor") {
                throw RuntimeException("KTOR FOUND!")
            }
        }
    }
}```

hum..I have to add in my case project B is a kotlin multiplatform project...and I don't see the dependency in the scan

With `implementation(lib)` in B, then the `compileClasspath` in A won't have `lib` in it (that's the point of `api` vs `implementation`). Maybe just check `runtimeClasspath` instead?

BTW, how about a dependency constraint with `version { rejectAll() }`? (wouldn't work for a groupId only, requires an artifactId too)

no luck because it's not really there...I think it's an issue of kotlin MPP -&gt; kotlin jvm

That works...

```configurations.default {
    resolutionStrategy {
        eachDependency {
            if (requested.group == "io.ktor") {
                throw RuntimeException("KTOR FOUND!")
            }
        }
    }
    resolve()
}```
but I'm terrified

ok...you where right, runtimeClasspath is it, but I need to resolve it and `assemble` is not resolving it

Maybe using "resolution consistency" with `useRuntimeClasspathVersions()` would resolve it whenever the compile classpath needs to be resolved; but that kind of resolution consistency might not be what you want…

test task resolves it (and publishing tasks) so it's fine, I dropped the `resolve()`

Alternatively, add your `project(B)` dependency in such a way that its `runtimeElements` variant is always used (rather than the `apiElements`  variant)

right now it's simply:
```dependencies {
    implementation(project("B"))```

Out of memory, something like:
```implementation(project("B")) {
    attributes {
        attribute(Usage.USAGE_ATTRIBUTE, objects.named(Usage.JAVA_RUNTIME))
    }
}```
(no idea if that would actually work though!)

hehehe, I'll try to understand what it does..

I think the current solution is good enough, and the issue with the approach you suggested is that it needs to be applied to all dependencies.

anyway, thanks a lot for helping!