It is in fact the project you are trying to run that is at fault here.
Wicket doesn't prescribe which logging framework one should use.
Therefore the examples projects need to choose their own logging
implementation. This holds for the wicket-examples from Apache as well
as for wicket stuff related projects.
Therefore, <scope>test</scope> is correct (for the wicket framework libraries).
Martijn
On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote:
Hello, wicket-dev,
Now I'm viewing wicket stuffs und some projects not started under
mvn jetty:run reason of
...
2007-06-13 09:32:42.952::INFO: jetty-6.1.4rc1
2007-06-13 09:32:43.687::INFO: No Transaction manager found - if your webapp
requires one, please c
onfigure one.
2007-06-13 09:32:44.155::WARN: failed wicket
java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:57)
at
org.apache.wicket.protocol.http.WicketFilter.<clinit>(WicketFilter.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
....
I'm using trunk version of the Wicket and jdk 1.5.
Artefact slf4j-log4j12-1.3.1.jar is not included into startup
classpath for jetty! Removing line 411 in the pom.xml
will bug disappear.
${trunk}/pom.xml
408 <dependency>
409 <groupId>org.slf4j</groupId>
410 <artifactId>slf4j-log4j12</artifactId>
411 <scope>test</scope>
412 </dependency>
Could this line be removed from pom.xml?
May be file a Jira issue?
--
Oleg Taranenko
mailto:[EMAIL PROTECTED]
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
