Classpath contains multiple SLF4J Bindings - unwanted debug log

[chris-aeviator]

Description

whenever importing the GraknClient and having already used another logger (e.g. slf4j) I will get a warning and much more dramatic, an automated enabled debug mode for my whole project. It turns out dramatic, since importing graknclient will also enable my Kafka debug log, which prints hundreds to thousands of messages per minute.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/korny/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/korny/.m2/repository/org/jboss/slf4j/slf4j-jboss-logging/1.2.0.Final/slf4j-jboss-logging-1.2.0.Final.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Environment

1.Linux 2. Latest 3. client-java latest 4. Other environment details:

Reproducible Steps

1. org.slf4j.Logger; import org.slf4j.LoggerFactory;
2. import GraknClient

[alexjpwalker]

Thanks for the report. We need to look into the behaviour of logback / SLF4J when the classpath contains multiple logging configurations.