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

Gradle Community

My plugin depends on a lot of plugins too, like Kover, Detekt and so on. If one of those plugins is using `1.7.10`, can it be the problem?

How can I force to avoid that dependency to be propagated so? The idea is that the consumer decides which Kotlin plugin must be used, that is the reason I am using `compileOnly`

I guess I have to exclude kgp for all of those plugin dependencies (or at least find which is use implementation instead of compileOnly to exclude it there)

Gradle classloaders are known to do surprising things. 
But nevertheless, looks like you need to support 2 versions of KGP at the same time? If some symbols changed between 1.6.10 and 1.7.0, your best bet is certainly some reflection

Yeah.. I was trying to avoid that,  so I am migrating everything to 1.7.10