From: Jan B. <ja...@mo...> - 2006-03-18 08:49:33
|
Hi Jurgen, Neither jetty6 nor the maven plugin contains commons-logging. We use the jcl104-over-slf1j.jar instead (see http://www.slf4j.org/manual.html#gradual) In fact, the plugin takes steps to ensure commons-logging is excluded from any dependencies. Is commons-logging in any of the dependencies or transitive dependencies for your webapp? This will have been revealed in beta12 as we changed the default loading behaviour to be webapp loader first (as per the servlet spec) instead of parent loader first (as per java 2). I will look at supporting the setParentLoaderPriority() priority as a configuration param for the plugin. Also, we would like to exclude commons-logging completely from jetty6, as it is only used by the jsp engine, which is Jasper. There have been some recent emails on this list about taking the logging out of Jasper and releasing this modified version with jetty (see the thread "Jasper JSP for jetty6!"). regards Jan Jurgen Lust wrote: > Hi, > > I've tried using the jetty6 maven plugin version beta12 today, and it > seems to have a problem with log4j and commons-logging. > It is the problem described in example 4 here: > http://www.qos.ch/logging/classloader.jsp > namely the Invalid class loader hierarchy exception. The problem only > occurs when using the mvn jetty6:run command, and when the project is > reloaded for the first time after a change in the project sources. > I thought version beta12 no longer contained the commons-logging jar > file, but this seems to indicate that it does. > I do not have this problem when using version beta9. > > Kind regards, > > Jurgen > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 |