On Tue, 1 Apr 2003, Martin Monsorno wrote:
> Date: Tue, 01 Apr 2003 16:42:32 +0200 > From: Martin Monsorno <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: "Niesen, Nathan" <[EMAIL PROTECTED]> > Cc: 'Edgar Dollin' <[EMAIL PROTECTED]>, > 'Struts Users Mailing List' <[EMAIL PROTECTED]> > Subject: Re: how to switch of logging with log4j at initialization > > "Niesen, Nathan" <[EMAIL PROTECTED]> writes: > > There is a bug in commons-logging 1.0.2+ that causes log4j to be used if > > it's found in the classpath. Just remove the log4j jar from your webapps > > lib dir. > > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17561 > > > > There is also a bug in the commons-logging nightly build, which is what the > > current Struts build uses, that causes the commons-logging.properties to be > > ignored. > > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17894 > > As I wrote as an answer to Edgar Dollin, my problem is not that log4j > is used, but that my log4j configuration seems to be not the only one > used, as I set the logging for "com.apache" to a file with ERROR > level, but the output for (some of?) the commons-classes is logged > anyway to stdout. > Assuming that "com.apache" is not a typo, you might try "org.apache" instead. > -- > Martin Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
