I am not using maven but gradle, but otherwise:
* there is only one logback jar on the classpath
* there are no configuration files anywhere - I had checked this before
But there may be programmatic configuration somewhere, and as I am seeing a
lot of wicket DEBUG output, I thought it were wicket's doing.
On Tue, Oct 23, 2012 at 9:24 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Wicket comes only with slf4j-api.jar. The application developer should
provide the implementation.
Check with 'mvn dependency:tree' that there is no other SLF4J impl
than yours (logback).
Additionally with ClassLoader#getResources(/logback.xml)
(logback-test.xml, logback.groovy, log4j.properties) you may find
whether there is one of those in the classpath and where exactly.
On Tue, Oct 23, 2012 at 1:31 AM, Wujek Srujek wujek.sru...@gmail.com
Hi. I am using wicket 6.1.0 and logback-classic as my logging backend.
There is no configuration anywhere but wicket (and wicket only) logs
everything at level DEBUG - where can this be coming come from?
Training, Consulting, Development
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org