You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a sample that I've been working for a blog post that I'm writing. If you download that code and run jettyRun you should get the the error and the stack trace. I'm attaching a part of the log:
I'm running in Oracle Java 7.0.60:
------------------------------------------------------------
Gradle 1.10
------------------------------------------------------------
Build time: 2013-12-17 09:28:15 UTC
Build number: none
Revision: 36ced393628875ff15575fa03d16c1349ffe8bb6
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.2 compiled on July 8 2013
Ivy: 2.2.0
JVM: 1.7.0_60 (Oracle Corporation 24.60-b09)
OS: Mac OS X 10.9.3 x86_64
The text was updated successfully, but these errors were encountered:
Thanks for looking into this. I was stuck for a few days until I finally managed to scope down the problem. Do you know what exactly this is all about? Adding logback sounds more like a work around. If someone would like to use some other logging implementation with SLF4J, this may not be an option.
I'm actually getting this problem on JDK-8.. it was working perfectly until today and now the whole hell broke loose and it doesn't seem to be working for me anymore :(
I started having this problem after I updated from version 0.0.17 to 0.0.24. It seems that it started happening between version 0.0.23 and 0.0.24.
It seems to be some conflict between SLF4J versions from Jetty and the one I and Spring are using. I'm using only API version 1.7.6. You can see the whole code here: https://github.com/visola/bearprogrammer-examples/tree/master/gradle-integration-test
It's a sample that I've been working for a blog post that I'm writing. If you download that code and run jettyRun you should get the the error and the stack trace. I'm attaching a part of the log:
I'm running in Oracle Java 7.0.60:
The text was updated successfully, but these errors were encountered: