On Jun 28, 2007, at 6:06 PM, Paul Smith wrote:
Hi Curt,
I have not yet worked out how to do this yet, but I thought I'd
mention it before we perform a release of the Receivers module.
Chainsaw will need to be shipped with a cut-down version of the
receivers package due to Classloading rules. The Receivers that
depend on 3rd-party drivers cannot be packaged up with Chainsaw.
Those Receivers will need to be downloaded separately by the user
together with their driver jars and placed in their local plugins
directory.
Is there a way with maven assemblies to create:
* standard assembly as we have now
* receivers-chainsaw - receivers distro without DBReceiver,
JMSRecevier or VFSLogFilePatternReceiver
* receivers-chainsaw-extras - inverse of receviers-chainsaw
(names can obviously be changed)
That way Chainsaw can be shipped with receviers-chainsaw, and we
can provide a link for the user to download and install the others.
I'm actually considering modifying Chainsaw to be able to
automatically soak it for them.
Is this possible?
cheers,
Paul
Will have to think about that. One possibility would be to spin DB,
JMS and VFS each off to a separate companion. Wasn't thinking when
we were were going down this path that we'd end up with as many
companions as we have. I don't think it is unmanageable, but maybe
we should consider rolling all the companions that have just log4j
1.2.9 and oro dependencies back into an "extras" companion (filters,
logmf, logsf, pattern layout, rolling, sound). I could likely put
one together pretty quickly for evaluation.
We probably need to review the NOTICE files on all the companions
that reference non-ASF jars to make sure that we properly acknowledge
use of other projects. I was thinking that Zeroconf may need one due
to the JmDNS library.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
