| Re: [orbit-dev] Orbit should promote a new build with the new certificate |
I've no problem spinning a new S-build, promoting it, and announcing it to M5 orbit consumers ... but, I'd prefer to wait until it was known for sure it was needed.
Having something signed multiple times, by multiple certificates, should not be a problem.
http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/jarsigner.html
If it is a problem for us, I suspect there's another issue or bug somewhere. So I'd hate for us to mask some other problem, just by working around it by forcing the same certificate. I've seen similar problems in the past, and it was actually caused by re-conditioning a signed jar, not signing it twice. Also, the platform consumes several jars from Orbit, besides junit. It'd be odd that only one was effected.
I have forced another I-build, just so it uses the new certificate, and we can 'verify' they are signed correctly at the source. If Kim or platform build needs something to test or compare, they can use that.
Martin, I suspect you tried to kick off an S-build, but it is in the "paused" state, so even a manual trigger won't build it, it has to be taken out of paused state first.
Also, declaring, or, promoting, a build does require special permission on the build and download machine ... DJ or I can to that Monday if required.
I appreciate you being pro-active, though, so we'll all be 'on high alert' for quick reaction on Monday.
Thanks,
"Oberhuber, Martin" ---02/01/2009 07:04:12 PM---Hi all,
From: | "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx> |
To: | "Orbit Developer discussion" <orbit-dev@xxxxxxxxxxx> |
Date: | 02/01/2009 07:04 PM |
Subject: | [orbit-dev] Orbit should promote a new build with the new certificate |
Sent by: | orbit-dev-bounces@xxxxxxxxxxx |
