One thing I found about commons logging is that you are forced to use log4j as long as it's on the classpath (if I remember correctly). Also, Velocity is hardwired to using log4j. I don't see any advantage to it right now. I'm +1 on your proposal.
Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > -----Original Message----- > From: Harald Ommang [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 29, 2003 1:22 PM > To: [EMAIL PROTECTED] > Subject: RE: Unless any objections: someone please update to > Commons Logging 1.0.3 and LOG4J 1.2.8 > > > On Wed, 28 May 2003 22:05:13 -0500, "Mark Orciuch" wrote: > > > > > I hate to say this but upgrading to Commons Logging 1.0.3 broke > import task > > in the build - didn't look into it too much but looks like a > JDK dependency > > issue? Jetspeed releases are built with JDK 1.3 and that is > what I'm using. > > > > Oops... > > OK, My suggestion is: > > * Roll back to CL 1.0.2 (But keep log4j-1.2.8 > * I can use LOG4J directly in the JetspeedLogger wrapper, not > Commons Logging. > This can be changed at any time transparently to users of the > JetspeedLogger. > (Which will be attached to bug 19906 soon...) And after having read Ceki > G�lc�'s comments on using Log4J via Commons Logging, i lean > against skipping CL > and going directly, anyway. > > Harald > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
