Monday, January 12, 2004

Another follow up to Fighting with Java logging.  It appears there has been a thread about Lumberjack and Commons Logging on the Commons user mailing list.  However, there doesn't appear to be a good resolution.  Hrmph. 1:39:38 PM    comment []

Here's a follow-up to Fighting with Java logging.  I've found that alot of the Jakarta libraries and other open source libraries are using Commons Logging to abstract the logging for their library.  This makes alot of sense - they don't have to worry about whether you are using JDK 1.4 logging of whether you are using Log4j.  However, if you are using Lumberjack, you are screwed.  Let me rephrase that: if you are using Lumberjack, and you don't have time to fiddle with the source for Lumberjack to add the missing method from JDK1.4 or add support for Lumberjack to Commons Logging, then you are screwed.  In my case, I'm screwed. So far, I can't use Commons BeanUtils or StrutsTestCase.  Not happy.  I guess I should post a question to a Lumberjack list or something. 1:06:19 PM    comment []

© Copyright 2004 Tom Pierce.