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

Gradle Community

try changing

```implementation(files(libs.javaClass.superclass.protectionDomain.codeSource.location))```
to

```api(files(libs.javaClass.superclass.protectionDomain.codeSource.location))```

I presume that `build-logic/kotlin-library/build.gradle.kts` defines a dependency like this?

```implementation(project(":commons"))```

Sadly, tried api instead of implementation, but no luck.

Yes, that dependency is declared indeed

I think you’re just going to have to declare the dependency twice

```implementation(files(libs.javaClass.superclass.protectionDomain.codeSource.location))```


into `kotlin-library/build.gradle.kts` i suppose, already tried that too :grimacing:

No matter what you try, my hack-around will simply not work in that situation for the same reason you also cannot use it within `plugin { ... }` blocks.

The `plugins { ... }` block is extracted and applied to a dummy project to determine which type-safe accessors to generate.

In that dummy project the `LibrariesForLibs` is not present, but it is an essential part of the hack-around that the exact same version catalog is present on the project where you apply it as it on the project where you build the convention plugin.

And exactly that invariant is not given if you apply the one convention plugin inside the `plugins { ... }` block of the other one.

Ok I get it! Crystal clear as always, thanks for the explanation :+1: