Martijn Dashorst wrote: > > Yes, > > You need to define your own logging implementation. For log4j this is: > > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > </dependency> > > (add version yourself, best put in a dependencyManagement part). > > Martijn > Thanks! That's exactly what we needed to know.
This is no big deal to add, but out of curiosity, is this something new? Our builds have been running fine without this on all previous 1.3-SNAPSHOTs, and if it's a dependency of Wicket now, why is it not indicated in the Wicket pom? I assume it's because it might be different depending on which logging library one uses, but it is a little unfortunate that this technique kind of limits one of the nice benefits of using maven; automatic dependency resolution. Anyway, thanks for the the information. Once I manually added that dependency we were back up and running. -- View this message in context: http://www.nabble.com/remove-test-scope-for-slf4j-in-pom.xml-tf3913261.html#a11203528 Sent from the Wicket - Dev mailing list archive at Nabble.com.
