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). 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: Fri 7/4/2008 10:55 PM To: Log4J Developers List Subject: Re: Receivers artifacts and Chainsaw On Jul 4, 2008, at 12:28 PM, Thorbjørn Ravn Andersen wrote: > Paul Smith skrev den 04-07-2008 02:02: >> >>> >>> I think that there should be a core log4j which should cover those >>> classes described in the printed manual, and that all the other >>> stuff which has come up since then should go in one or more >>> "extras" packages which may have a different release cycle than >>> the core. >>> >> >> But there is.. log4j-receivers is a separate maven module with an >> independent release cycle. There's also log4j-extras. > Great. Somehow I must have missed the explanation of this on the > web pages, sorry. > > What is the state of the log4j-receivers and log4j-extras modules? > Extras 1.0 was released in August 2007. Receivers has not been released, but I don't know of any blocking bugs. It has just been waiting for a push to get Chainsaw and its dependencies released. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
