Using slf4j-simple binds the SimpleLogger implementation, conflicting with any logger configured by the application using the Java tracker.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/kirwin/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-simple/1.7.7/8095d0b9f7e0a9cd79a663c740e0f8fb31d0e2c8/slf4j-simple-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/kirwin/.gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-classic/1.1.3/d90276fff414f06cb375f2057f6778cd63c6082f/logback-classic-1.1.3.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]
As indicated here, libraries should only declare a dependency on org.slf4j:slf4j-api
The workaround is to explicitly exclude this transitive dependency when including the Java tracker artifact.
Using slf4j-simple binds the SimpleLogger implementation, conflicting with any logger configured by the application using the Java tracker.
As indicated here, libraries should only declare a dependency on org.slf4j:slf4j-api
The workaround is to explicitly exclude this transitive dependency when including the Java tracker artifact.