logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: DO NOT REPLY [Bug 17260] - Add a LogLog.getQuietMode() method
Date Fri, 21 Feb 2003 08:09:02 GMT

At 22:23 20.02.2003 +0000, you wrote:
>------- Additional Comments From hoju@visi.com  2003-02-20 22:23 -------
>Hi Ceki,
>Will LogLog stay there for backward compatibility and just be deprecated or
>will it be removed altogether as you seemed to imply?
>My servlet initializers in the log4j-sandbox use LogLog.  Will this make them
>incompatible with Log4j-1.3?

Good question. My inclination is to remove LogLog so that component 
developers would immediately see where they were calling LogLog (because 
their code would not compile.) Moreover, letting LogLog survive will almost 
certainly lead to a situation where some internal logs would go through 
log4j while others through LogLog. This will certainly confuse users.
Just as imortatnly, migrating from LogLog to "log4j" is rather easy. Just 
change LogLog to logger.debug or logger.info (one also has to retrieve the 

I'll write up a document on how to use log4j from within log4j components.



To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

View raw message