The ant build.xml can has a 'webstart-dist' target and an 'iOrb' type target. They generate and sign the jar files (it prompts you for a local keystore and certificate passwords during the signing process; I have my thawte certificate loaded in a keystore locally). I think I had a target that uploads those signed stuff to the area where the Webstart bundle is kept, but due to symlink weirdness with Webstart, there's still a bit of hand moving of files around during the deployment.


log4net requires signed assemblies and until recently only Nicko was able to produce them. He has recently placed an encrypted signing key in the SVN so that Ron or I can also produce builds of log4net. Would we'd want to do the same type of thing for Chainsaw?


The main problem here is that the signature being signed with is my own personal one containing my @apache.org email address. To get the email certificate properly certified, I had to get 2 Thawte signatories to meet me in person and check documentation. I'm not sure how one gets around that for a generic 'log4j' certificate. I'm not sure I'd like to upload my signature that anyone could sign it with.

Having said that, if we can work out how we can generate a certificate that all the logging services people can use, I'd vote for that. Can you explain exactly how the certificate was generated for log4net?


I'm going to sleep now. I may take a run at LogFilePatternReceiver tomorrow unless you want to take it.


I thought you were going to sleep!  Are you still in US Central TZ?




I've got the source file change tool down, so I'll take a pass at applying the tool to the chainsaw code base tomorrow unless someone calls me off (for example, if you have a lot of uncommitted changes).

Nothing local changed at all, save for the application of that patch you sent to change the log4j 1.3->1.2 dependency, which can be easily redone if need be.

Paul




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to