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

Gradle Community

try taking a look at <https://github.com/ljacomet/logging-capabilities>

even if it builds, a plugin will be loaded into Gradle's classpath at runtime, where the slf4j implementation will be the one from Gradle and not whatever the library wants

e.g. that library is just incompatible with being used in a Gradle plugin

<@U019L3NM4PK> what would be your recommendation in this case? Rewrite the java libraries to be compatible w/ the plugin’s logging library?

I’m assuming that I won’t be able to rewrite the plugin without using the `groovy-gradle-plugin` and thus rewriting the plugin is not a viable solution for my use case?

it doesn't matter if you create the plugin via `groovy-gradle-plugin` or manually set up the compilation and output, it simply can't work at runtime

you'll have to either fix the java library or use something else

Yeah it's a class path issue so as is how things are done, you should probably pick the latest backwards compatible library. But yes, you don't get much of a choice in java lands