Howdy,
Seems like a good idea: the struts/log4j case is very common from what
I've seen, and moreover I think it's a best-of-breed/best-practice
configuration that we want to support seamlessly.
What do you need in terms of dependencies, other than commons-daemon?
I'll push a commons-daemon 1.0
Shapira, Yoav wrote:
Howdy,
Seems like a good idea: the struts/log4j case is very common from what
I've seen, and moreover I think it's a best-of-breed/best-practice
configuration that we want to support seamlessly.
That's the idea. Now that I got it to run well, I like commons-logging :)
What do
On Mon, 8 Sep 2003, Remy Maucherat wrote:
Date: Mon, 08 Sep 2003 16:48:52 +0200
From: Remy Maucherat [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: Re: [5.0] Planning
Shapira, Yoav wrote:
Howdy,
Seems like
Craig R. McClanahan wrote:
On Mon, 8 Sep 2003, Remy Maucherat wrote:
Howdy,
Seems like a good idea: the struts/log4j case is very common from what
I've seen, and moreover I think it's a best-of-breed/best-practice
configuration that we want to support seamlessly.
That's the idea. Now that I got
On that topic, is there a reason that Tomcat 5.0.x still uses
commons-logging-api.jar instead of commons-logging.jar? If you're
putting
this jar in common/lib, you'd avoid the need for webapps to have to
include commons-logging.jar themselves in order to use the default
functionality.
Craig,
Jan Luehe wrote:
On that topic, is there a reason that Tomcat 5.0.x still uses
commons-logging-api.jar instead of commons-logging.jar? If you're
putting
this jar in common/lib, you'd avoid the need for webapps to have to
include commons-logging.jar themselves in order to use the default
