On 5/13/2009 9:26 PM, Paul Smith wrote:
>>
>> Can't yank it from log4j.jar without potentially breaking some app
>> that actually uses it, but could mark it as deprecated and suggest
>> checking the jmx companion.
>
> the alternative is to start yanking things out of log4j into a 'legacy'
> jar.
Can't yank it from log4j.jar without potentially breaking some app
that actually uses it, but could mark it as deprecated and suggest
checking the jmx companion.
the alternative is to start yanking things out of log4j into a
'legacy' jar. People that wish to upgrade log4j jars, need perh
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 exis
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 cl
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
comp
My changes are in (Chainsaw find next/clear find next context menu items and
enhancements to vfs/logfilepatternreceiver).
I should have added the find next/clear find next to menus but I've ran out
of time for now...
Scott
On Tue, May 12, 2009 at 10:26 PM, Scott Deboy wrote:
> I have a couple
I have a couple of additions to make to
Chainsaw/LogFilePatternReceiver..should be done tonight hopefully..
On Tue, May 12, 2009 at 9:59 PM, Curt Arnold wrote:
>
> On May 12, 2009, at 5:36 AM, Stefan Fleiter wrote:
>
> Sorry, I have to correct myself:
>>
>> https://issues.apache.org/bugzilla/s
On May 12, 2009, at 5:36 AM, Stefan Fleiter wrote:
Sorry, I have to correct myself:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44308
This bug contains a patch for JMX Management of Log4j Appenders and
their log levels.
The levels of *loggers* can be configured.
Sorry hadn't foll
Sorry, I have to correct myself:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44308
This bug contains a patch for JMX Management of Log4j Appenders and
their log levels.
The levels of *loggers* can be configured.
-
To
Curt Arnold wrote:
If you have a bug that you'd really like to see integrated and there is
an available patch or the solution isn't a totally rearch of log4j,
please speak up.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44308
This bug contains a patch for JMX Management of Log4j Appende
If you have a bug that you'd really like to see integrated and there
is an available patch or the solution isn't a totally rearch of log4j,
please speak up. I hope to cut a release candidate this week. Will
try to make a sweep through the open bugs for ones that can be
resolved, but might
11 matches
Mail list logo
