search

melix / jmh-gradle-plugin

Integrates the JMH benchmarking framework with Gradle
Apache License 2.0
666 stars 88 forks source link

JMH putting gradle logging jar on classpath, causing logback conflict #135

Open pkolaczk opened 6 years ago

pkolaczk commented 6 years ago 
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/pkolaczk/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/pkolaczk/.gradle/wrapper/dists/gradle-4.2.1-bin/7w84ql4sm9wo2z8zmgvxj021k/gradle-4.2.1/lib/gradle-logging-4.2.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

This is happening when trying to benchmark a project that already uses logback, in forked mode. Is there any workaround for this?

ryan-cook-18 commented 5 years ago

Have you found a solution to this?

pkolaczk commented 5 years ago

No, not really. We've been just ignoring the warnings.