[orbit-dev] new stable build S20090202130207

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

I promoted a new stable Orbit build
this morning.  

http://download.eclipse.org/tools/orbit/downloads/drops/S20090202130207/

The Eclipse foundation for installed
a new certificate on Friday that caused problems the Eclipse project's
build.  See these bugs for further details. 

promote 3.5M5
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263032
 

Certificate will expire within six months
https://bugs.eclipse.org/bugs/show_bug.cgi?id=252879
 

The new certificate was requested with
a new CSR instead of using the existing CSR and requesting a renewal of
the existing certificate. This caused problems for nested jars within a
bundle - they were signed with a new certificate which invalidated the
existing certificate.  Denis is investigating to see if he can renew
the existing certificate with the old CSR instead of requesting a new one.
I'll also exclude all Orbit bundles from being signed and packed in our
build in the future.

Discussion topic:  In either case,
it seems the binary content of the Orbit bundles has changed but the qualifiers
have remained the same.  Should all the orbit cvs bundles be tagged
with new versions to change the qualifiers to notify consuming clients
that there is new content?  Otherwise, there isn't a way to signify
to the community that the content of the jars in the two builds are not
identical.   I would propose that this should be done for the next
milestone, not M5.

Kim