On Jul 5, 2008, at 1:27 AM, Scott Deboy wrote:
When does the previous version of Chainsaw get taken out of log4j jar?
Earlier this week I responded to questions about how to configure
Chainsaw to use receivers. It turns out he was using the old
version of Chainsaw.
Would be nice to avoid that sort of issue (and shrink the core log4j
footprint in the process).
The classes in org.apache.log4j.chainsaw that are included in log4j
aren't marked as deprecated and so haven't even started the process
toward elimination. The first step should be to mark them as
deprecated and make sure that package.html explains the situation.
There definitely out in log4j 2, but think they have to stick in until
then.
Fortunately, there doesn't seem to be any class names that appear in
both the log4j embedded Chainsaw and the independent chainsaw.
Otherwise, I'd suggest changing the package name used by chainsaw.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
