org.slf4j v1.7.25 and v1.8.0-beta4 included

When using your package using gradle on java 11 I get following error

Error:java: module org.pf4j reads package org.pf4j from both slf4j.api and org.slf4j

When checking the files gradle loads and downloads I see org.pf4j is the only one including old version and a new version at the same time of the org.slf4j version.

I tested this both v2.6.0 and v3.1.0 both having the same affect. How can I not use org.slf4j v1.7.25 and exclude it during build / runtime?

Thanks for the help

[Douglasdc3]

Thanks @decebals you helped me dig down to the right package that was causing the issue

multiple packages are trying to claim slf4j implementation. jcl-over-slf4 (spring boot), logback and slf4j itself. I simplified the gradle file and it now only includes the slf4j api and spring boot adds a concrete logging framework.

Thanks for helping me discover this. I’m not that familiar with gradle either. You have a really easy and nice to use plugin module

[decebals]

As I said. I am not a Gradle connoisseur, but I feel that you are not interpreting the result correctly. I think that is similar with what is in Maven. So, ch.qos.logback:logback-classic has a direct dependency at org.slf4j:slf4j-api:1.8.0-beta1. The line org.slf4j:slf4j-api:1.7.25 -> 1.8.0-beta1 says that PF4J has slf4j-api:1.7.5 as dependency but Gradle will substitute this version with 1.8.0-beta1. Probably it’s the default strategy of how Gradle pick a version from multiple versions. If you remove ch.qos.logback:logback-classic than you will see (probably) that 1.8.0-beta1 will disappear.

But in the end I don’t know where is the problem if you go with 1.8.0-beta1 in your application.