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
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:/app/libs/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
and no additional logging happens no matter the --env LOG_LEVEL=xxx that you set in the docker run command line.
The text was updated successfully, but these errors were encountered:
* fixes#388 by upgrading slf4j to 2.x
* spring boot tests were failing due to Spring 2.7.x requiring slf4j 1.7.x
* added spring.factories to prevent Spring from using its LoggingSystemLogback class causing a NoClassDefFoundError on class removed from slf4j 2.x
* add sample docker-compose.yaml to easily test standalone mode
…394)
* fixes#388 by upgrading slf4j to 2.x
* spring boot tests were failing due to Spring 2.7.x requiring slf4j 1.7.x
* added spring.factories to prevent Spring from using its LoggingSystemLogback class causing a NoClassDefFoundError on class removed from slf4j 2.x
* add sample docker-compose.yaml to easily test standalone mode
Starting the docker image results in
and no additional logging happens no matter the
--env LOG_LEVEL=xxx
that you set in thedocker run
command line.The text was updated successfully, but these errors were encountered: