Ignite examples and Ignite itself with some configurations prints out
annoying messages related to slf4j:
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
The reason for these messages is inside
org.springframework.data:spring-data-commons. It adds a dependency to
jcl-over-slf4j that "activates" slf4j. slf4j then tries to find
slf4j-TO-SOMELOGGER to forward all messages to SOMELOGGER. Actually, it does
not result in any issues with Ignite logging itself, it just confusing
So, there are two options here to avoid these annoying messages:
1. exclude jcl-over-slf4j dependency from spring-data-commons in Ignite .pom
2. add slf4j-TO-SOMELOGGER (for instance, slf4j-log4j12 for log4j, or
Please advice on a better solution here.
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/