no i don't think Al lost, 1.4.2 or 1.4.3 that shouldn't matter But somewhere in your classpath you have and old version of 1 of the jars
Please start the java process up with -verbose:gc and see what jar file it gives for org.slf4j.Logger johan On 11/4/07, landry soules <[EMAIL PROTECTED]> wrote: > > Sorry Al, but you lost your money ;-) > > I put back slf4j-api-1.4.2.jar , and still the same problem... Using the > jars suggested by Cristi doesn't help either. But since it seems i'm the > only one to still have the problem, must be a problem with my classpath. I > will recheck after deploying the project in a war. Maybe it's just eclipse > WTP that does some weird things with my classpath. > As always, thanks a lot for your support, guys. > > 2007/11/3, Al Maw <[EMAIL PROTECTED]>: > > > > landry soules wrote: > > > Actually, i didn't go on with maven, since my project is already quite > > > advanced now, i don't want to reconfigure it to use maven. I just > tried > > to > > > create a sample project to figure out what is the correct combination > of > > > slf4j/log4j to use (bad idea, since it appears to be broken in the > > original > > > wicket pom). > > > So i'm back in my real eclipse project, and this neverending error : > > > > > > Exception in thread "ModificationWatcher Task" > > java.lang.NoSuchMethodError: > > > org.slf4j.Logger.isTraceEnabled()Z > > > at org.apache.wicket.util.thread.Task$1.run(Task.java:103) > > > at java.lang.Thread.run(Thread.java:595) > > > > > > even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar. > > > > You also need slf4j-api-1.4.2.jar. I'd lay money on your not having that > > version on your classpath (or having an earlier version as well). > > > > Regards, > > > > Al > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
