At 22:23 20.02.2003 +0000, you wrote:
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.------- Additional Comments From [EMAIL PROTECTED] 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?
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 logger.)
I'll write up a document on how to use log4j from within log4j components.
--Jake
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
