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
function
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, yo
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 it
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 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
mons-daemon 1.0 RC and then final releases in the next
couple of weeks.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Remy Maucherat [mailto:[EMAIL PROTECTED]
>Sent: Sunday, September 07, 2003 10:15 AM
>To: Tomcat Developers List
>Subject: [5.0] Plannin
Rather than having a vote for 5.0.10, I'd like to release a new 5.0.11
build with the fix for the (nasty) commons-logging classloading issues.
The idea is that using Struts 1.1 with log4j is quite common, and using
that in conjunction with a context config file cut & pasted from the
manager or
