logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jess Holle <je...@ptc.com>
Subject Re: log4j 1.2.16 RC1: last call for bugs
Date Thu, 14 May 2009 03:05:21 GMT
Curt Arnold wrote:
> On May 13, 2009, at 6:19 AM, Jess Holle wrote:
>> Curt Arnold wrote:
>>> Sorry hadn't followed that one.  It seems like a good replacement 
>>> for some not ready for primetime code that has been in log4j for a 
>>> while.  However, since it is all new code and not any modifications 
>>> to existing log4j classes, it would make a good candidate for a 
>>> log4j companion.  In a perfect world, they should be able to rev 
>>> faster than the main log4j release.
>>> I'll see about packing that up in the sandbox as a companion and see 
>>> if we can get any feedback on it.
>> Agreed.  I'd long since given up on this being fixed and written my 
>> own JMX monitoring classes for log4j.
>> Given use cases like usage of log4j on the client, I'd rather not 
>> shove new JMX monitoring classes into the main log4j jar.  Instead 
>> providing these in an optional companion jar makes much more sense.
>> [For that matter given the state of the JMX classes that are present, 
>> it would be good to remove those...]
>> -- 
>> Jess Holle
Understood -- though a log4j-core.jar might be in order if there are 
other packages in a similar boat.

Of course I could just make a log4j-core.jar for my own usages as well.

Jess Holle

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

View raw message