Issue when using jetty plugin with

[Ricardo Mayerhofer]

Hi all,
I'm facing a problem when using JettyRunWar task and slf4j-jcl in my
application. The error shows up when starting the application:
Caused by: java.lang.IllegalStateException: Detected both jcl-over-slf4j.jar
AND slf4j-jcl.jar on the class path, preempting StackOverflowError. See also
http://www.slf4j.org/codes.html#jclDelegationLoop for more details.

It seems that the application dependency: slf4j-jcl-1.7.2.jar is conflicting
with gradle dependency: lib/jcl-over-slf4j-1.6.6.jar

Does JettyRunWar task inherit gradle classpath? Is there a way to workaround
this, for example starting Jetty on a different JVM or with a different
classpath?

Any help is appreciated.

Thanks.



--
View this message in context: http://gradle.1045684.n5.nabble.com/Issue-when-using-jetty-plugin-with-tp5710958.html
Sent from the gradle-user mailing list archive at Nabble.com.

[Luke Daley]

Hi Ricardo,

Post by Ricardo Mayerhofer
Hi all,
I'm facing a problem when using JettyRunWar task and slf4j-jcl in my
Caused by: java.lang.IllegalStateException: Detected both jcl-over-slf4j.jar
AND slf4j-jcl.jar on the class path, preempting StackOverflowError. See also
http://www.slf4j.org/codes.html#jclDelegationLoop for more details.
It seems that the application dependency: slf4j-jcl-1.7.2.jar is conflicting
with gradle dependency: lib/jcl-over-slf4j-1.6.6.jar
Does JettyRunWar task inherit gradle classpath? Is there a way to workaround
this, for example starting Jetty on a different JVM or with a different
classpath?

There's currently no way to fully isolate the classpaths unfortunately. I'd suggest using the Cargo plugin: https://github.com/bmuschko/gradle-cargo-plugin