Why can't the old version of Chainsaw simply be re-packaged into a separate
jar? I think lots of people would be happy to have a smaller log4j artifact
to deploy and those that want to use chainsaw version 1 simply add another jar
to their classpath. This has nothing to do whether we deprecate the classes
or not, though I'm not against doing that either. It's just a repackaging.
Jake
On Sat, 5 Jul 2008 10:46:22 -0700
"Scott Deboy" <[EMAIL PROTECTED]> wrote:
I don't have a problem with deprecating for one release, but I don't think
we need to keep them in there until log4j 2 - we aren't talking about an API
that folks are coding against and the bits never change, so folks interested
in using the original Chainsaw can just use an old version of log4j.
I'll mark the Chainsaw classes deprecated now and we can have the
conversation about removing them once the next release is out.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax: 503.222.0185
[EMAIL PROTECTED]
www.comotivsystems.com
-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Sat 7/5/2008 9:37 AM
To: Log4J Developers List
Subject: Re: Receivers artifacts and Chainsaw
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
