I'm in favor of moving to commons-logging. I planned on doing this a while ago (after having good luck with JCS) but then commons-logging changed completely and pushed out a rather unstable 1.0 release which scared me off. However JCS is now working fine against the current HEAD commons-logging (thanks dlr!). Moving in the same direction with the rest of the Turbine projects seems like the best solution.
I am also against upgrading to log4j 1.2 since it is still unreleased, and the release is supposed to remain compatible with 1.1, at least until early 2003. Thus any incompatibility is probably a bug in log4j. However abstracting it with commons-logging eliminates any concern about what version you or I use, so that is what I favor most, though I personally don't have the time to do it. -- jt > Looks like the Category class has been turned into the Logging class...so, I > guess my question is whether or not we should make the effort to switch > Turbine to the commons-logging stuff or upgrade Log4J? > > -jon > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
