You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the jsonld subproject's pom.xml, I see there are no explicit dependencies declared for either slf4j or logback, which means this project is at the mercy of whatever transitive versions of those that are brought in by the direct dependencies. The output of mvn -U -Dmaven.test.skip=true -Dverbose -DoutputFile=deps.txt dependency:tree shows a lot of conflicting versions for slf4j but the final "winner" is 1.7.36 even though most of the dependency's transitive slf4j dependencies are trying for 2.0.6 or 2.0.7, however after the resolution, version 1.7.36 wins.
I tried forcing slf4j-2.0.7 as suggested in https://www.slf4j.org/codes.html#StaticLoggerBinder but kept getting the same ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder - this was not new to me; I have run into this many times. My solution is to downgrade logback to 1.2.x from 1.3.x.
Summary - the Fix
Explicitly use versions for slf4j, using 1.7.32 and logback1.2.11.
The text was updated successfully, but these errors were encountered:
Hi,
thanks for reporting this! It is actually not necessary to fix the version of SLF4J and logback in the jsonld sample project, as they are already inherited from the parent.
The problem is that I merged a GH dependabot PR which upgraded logback to 1.3 which is not supported by Spring Boot 2. Sorry for the confusion, that is totally on me, as it wasn't the first time I ran into this compatibility issue. I should have remembered that:)
I switched to logback 1.2.13 in the parent project and now it seems to work fine. I'll close this issue and your PR (which is totally fine, but I want the version fixed in the parent project).
Feel free to reopen or comment if you encounter any more problems.
Upon running
mvn spring-boot:run
as advised in the subproject's README.md, Spring-Boot appears to start, then we get the error:I have never had advice suggested in the the URL https://www.slf4j.org/codes.html#StaticLoggerBinder to help. i.e. to push forward to to
slf4j-2.0.x
- rather,slf4j-1.3.x
still works.TL;DR
Looking at the jsonld subproject's pom.xml, I see there are no explicit dependencies declared for either
slf4j
orlogback
, which means this project is at the mercy of whatever transitive versions of those that are brought in by the direct dependencies. The output ofmvn -U -Dmaven.test.skip=true -Dverbose -DoutputFile=deps.txt dependency:tree
shows a lot of conflicting versions forslf4j
but the final "winner" is1.7.36
even though most of the dependency's transitiveslf4j
dependencies are trying for2.0.6
or2.0.7
, however after the resolution, version1.7.36
wins.I tried forcing
slf4j-2.0.7
as suggested in https://www.slf4j.org/codes.html#StaticLoggerBinder but kept getting the sameClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
- this was not new to me; I have run into this many times. My solution is to downgradelogback
to1.2.x
from1.3.x
.Summary - the Fix
Explicitly use versions for slf4j, using
1.7.32
and logback1.2.11
.The text was updated successfully, but these errors were encountered: