On Aug 20, 2007, at 10:56 PM, Paul Smith wrote:
I had a crack at working out how to create 2 separate artifacts for
the log4j-receivers module, 1 for the primary artifact (as current)
and one a chainsaw-specific artifact that excludes the JMS, DB and
VFS-based Receivers. This is needed for the Webstart version
because of the difference in classloaders being used.
Could you refresh me on the technical issue that you are trying to
work around? I looked in the archives and it didn't jump out at me.
I found this thread extremely useful and promising:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg68479.html
Which looked like it would work a treat, but unfortunately I hit
this issue with the maven-jar-plugin:
http://jira.codehaus.org/browse/MJAR-30
Given the 2nd artifact is really 'everything but these ones
excluded' without the exclude feature we're a bit stuffed.
I may have to resort to an antrun plugin usage to get what we
need. The build-helper plugin can still help us here (slight pun
intended).
Just thought I'd update everyone with where I'm at.
cheers,
Paul
It still seems to me that Webstart doesn't align well with the ASF
release infrastructure. I don't see a way for us to leverage the ASF
web of trust of GPG signatures to verify a signed jar and the current
Webstart version of Chainsaw isn't served through the mirrorred
distribution server and not archived. I also could not find a
release vote in the archives. I'm fairly uncomfortable with what we
have out there and would like to have a formal release.
There is nothing preventing a single individual or organization
repackaging a Chainsaw release for use with Webstart, but it seems
problematic as an official release mechanism. Could we have a tool/
script in the tarball/zip release that allows an individual or
organization to sign the jars with their signature to support private
webstart deployments? So we would send up with a tarball and zip
that would:
a) Could be run double clicking on the chainsaw jar (where supported)
or by "java -jar apache-chainsaw-2.0.jar").
b) Could be run on Mac OS/X platforms by clicking on Chainsaw.app
c) Could be jarsigned by running some script and then copied to a web
server for deployment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
