Jetty plugin exclude logback-classic - gradle lib dependency - from webapp classpath


(Eli Ezeugoh) #1

I have a project that uses log4j with slf4j but am getting the multiple bindings error because logback-classic somehow makes it into the classpath used by jetty when it starts up.

Any idea on how I can easily remedy this?

Many thanks

Eli


(Benjamin Muschko) #2

Probably Gradle core is already providing the logback JARs at runtime. log4j-over-slf4j-1.6.2.jar, logback-classic-0.9.29.jar and logback-core-0.9.29.jar are part of the lib directory so you might run into classloading issues. I am not quite sure if the Jetty plugin isolates them when you run your jetty tasks. Try to assign the configuration providedCompile to the logback dependencies in your project.