Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.11.2.7
-
Fix Version/s: 2.11.3.0
-
Component/s: Command Line Interface
-
Labels:None
-
Environment:CLI
Description
The SLF4J is missing a StaticLoggerBinder (which probably happened when upgrading during the log4j fixes) and produces a STDERR message
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
The further details explained the cause and fix, which is to add a jar with a StaticLoggerBinder class, e.g. slf4j-nop.jar (no-op).
The no-op jar is suitable because this is apparently what slf4j falls back to anyway.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
The further details explained the cause and fix, which is to add a jar with a StaticLoggerBinder class, e.g. slf4j-nop.jar (no-op).
The no-op jar is suitable because this is apparently what slf4j falls back to anyway.