Re: Clogging NoClassDefFoundError

2006-12-22 Thread Alexandre Poitras
From : http://cwiki.apache.org/WICKET/maven-jetty6-plugin.html *Currently, the best plugin version to use is the 6.0-SNAPSHOT one, so be aware that it is a little out on the edge. The reason for this is that earlier versions of Jetty used commons-logging, which lead to various class-loader issue

Re: Clogging NoClassDefFoundError

2006-12-18 Thread Jim Downing
Dennis Lundberg wrote: Hi Jim This is a Commons Logging - Log4J classic. It would take a while to explain it, but the short version is that Commons Logging and Log4J are probably in different classloaders. The best way to trace the source of the problem is to upgrade Commons Logging (temporar

Re: Clogging NoClassDefFoundError

2006-12-15 Thread Dennis Lundberg
Hi Jim This is a Commons Logging - Log4J classic. It would take a while to explain it, but the short version is that Commons Logging and Log4J are probably in different classloaders. The best way to trace the source of the problem is to upgrade Commons Logging (temporarily) to version 1.1. Th

Re: Clogging NoClassDefFoundError

2006-12-15 Thread Wayne Fay
Hmm in that case, I really have no idea why its failing. I don't use Jetty much less jetty:run. To be honest, it sounds like a Jetty question, since clogging and log4j are clearly on the Jetty classpath. Wayne On 12/15/06, Jim Downing <[EMAIL PROTECTED]> wrote: Wayne Fay wrote: > Check the log

Re: Clogging NoClassDefFoundError

2006-12-15 Thread Jim Downing
Wayne Fay wrote: Check the log4j-xyz.jar version referenced in your MANIFEST.MF and WEB config files against the log4j jar versions you've got in your WAR. This can happen when you for example reference log4j-1.2.2.jar in your MANIFEST but then load log4j-1.2.3.jar in your WAR. in a parent pom

Re: Clogging NoClassDefFoundError

2006-12-14 Thread Wayne Fay
Check the log4j-xyz.jar version referenced in your MANIFEST.MF and WEB config files against the log4j jar versions you've got in your WAR. This can happen when you for example reference log4j-1.2.2.jar in your MANIFEST but then load log4j-1.2.3.jar in your WAR. in a parent pom can help solve thi

Clogging NoClassDefFoundError

2006-12-14 Thread Jim Downing
Hi, I'm having problems with the jetty plugin - on running 'mvn jetty:run' I get a mysterious exception from clogging that is caused at some point by a NoClassDefFoundError complaining that it can't find log4j. Log4j is referenced by the project, ends up in the package war and is also listed