Stork had an API breaking change on the 1.1.x/1.2.0 boundary: slf4j-api 1.7.x -> 2.0.x
grossws opened this issue · comments
After bumping Quarkus version to 2.14.2.Final (which brings stork-core 1.3.0) I get the following error in the logs when running quarkusDev gradle task.
org.slf4j:slf4j-api::jar classpath entry /home/gross/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/1.7.36/6c62681a2f655b49963a5983b8b0950a6120ae14/slf4j-api-1.7.36.jar was overriden with /home/gross/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/2.0.3/deef7fc81f00bd5e6205bb097be1040b4094f007/slf4j-api-2.0.3.jar
Listening for transport dt_socket at address: 5005
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J: Ignoring binding found at [jar:file:/home/gross/.gradle/caches/modules-2/files-2.1/org.jboss.slf4j/slf4j-jboss-logmanager/1.2.0.Final/baff8ae78011e6859e127a5cb6f16332a056fd93/slf4j-jboss-logmanager-1.2.0.Final.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
It seems that Stork bumped slf4j-api somewhere between 1.1.2 and 1.2.0 but it isn't documented in the release notes as a breaking change.
Currently slf4j-jboss-logging/slf4j-jboss-logmanager (later used by Quarkus) support only slf4j-api 1.7.x (see https://issues.redhat.com/browse/JBLOGGING-165, jboss-logging/slf4j-jboss-logmanager#16).