Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <792294BC-E34A-4477-8018-0AACA1BA4995@aconex.com>
From: Paul Smith <psmith@aconex.com>
To: Log4J Developers List <log4j-dev@logging.apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Receivers artifacts and Chainsaw
Date: Fri, 4 Jul 2008 08:46:05 +1000

One of the last tasks to complete before a potential 'release' to the  
Webstart version of Chainsaw is building a custom Receiver artifact  
output that does not include the JMSReceiver & DBReceiver, both of  
which require dependent jars that we obviously can't ship (because we  
don't know what provider they'll need).

I plan to add a new output artifact in log4j-receivers that contains  
this, and have it with a classifier of 'chainsaw-receivers', and have  
it attached via buildhelper plugin so that it is pushed out as an  
artifact. A similar approach would be to produce an artifact just  
containing JMS+DB receivers.  There would still be a 'non-classified'  
binary containing all Receivers as standard.

That way Chainsaw can mark a dependency on it's relevant classifier.   
This would mean that both the Webstart and standalone versions of  
Chainsaw would require an end-user who wished to use JMSReceiver or  
DBReceiver could download the 'extras' pack of Receivers, and drop it  
into the plugins folder together with their provider jars.

thoughts?

Paul

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