From: Jan Bartel <janb@mo...> - 2006-08-27 15:33:36
Seems like .zip attachments are banned from the jetty lists.
So the email I sent below didn't make it to the list, so I'm
resending it minus the zip.
I've sent the zip to Dave privately. If anyone else would
like one, let me know.
-------- Original Message --------
Subject: Re: maven plugin, excluding slf4j dependency
Date: Sun, 27 Aug 2006 17:16:46 +0200
From: Jan Bartel <janb@...>
Organization: Mort Bay Consulting
To: Discussion for Jetty development. <jetty-discuss@...>
References: <e964bf$1be$1@...> <44B6B1F1.9050704@...> <5837146.post@...> <44E88669.3080804@...> <5894769.post@...> <44EC1E7D.501@...> <44EC81F3.2020402@...> <5995862.post@...> <5995878.post@...> <44F04684.6050902@...> <5998616.post@...> <44F16232.2020302@...> <6005749.post@...>
I don't necessarily think this is a problem with the logging.
Attached is a small example webapp that uses commons logging
and prints out 100 repetitions of a log message whenever you
hit http://localhost/my-webapp/index.jsp. It is working fine.
Note that the commons-logging jar is *both* a <dependency> and
a <plugin><dependency>. I've also excluded the servlet-2.3.jar
which is a transitive dependency of commons-logging.
I think 78 dependent jars might be a record of some sort! I think
with such a high number of jars there is every chance it is some
sort of incompatibility in there.
How do you know the app has fully initialized before the
Does your webapp work when you run it standalone?
Dave Syer wrote:
>>Instead of <slf4j>false</slf4j> in the pom.xml you need to use
>>-Dslf4j=false on the command line.
> Thanks. Tried it, and it made no difference (still getting
> StackOverflowError from jetty, after app has initialised). Also tried
> moving the commons-logging dependency out of the web app and into the
> plugin, and that gave the same result.