Re: [orbit-dev] Declaring Build: I20150412191215 - build improved - to b

[David M Williams <david_williams@xxxxxxxxxx>]

Apologies for the churn, but I think best
to remove this I-build. It was re-packed/packed with Java 8, but the Eclipse
Foundation infrastructure team has decided to revert that change, so now
this version may "more different" than I realized, and certainly
different from subsequent I-builds, moving back to Java 6. 

I believe even then we may have to "touch
everything" to make sure qualifiers are increased and set everything
straight with new certificate, and our Orbit move from Java 5 to Java 6
... but, at least we'll start a little closer by removing this one "Java
8" version. 

Apologies in advance to anyone who already
moved up to this version. Feel  free to tell us unanticipated complications
and/or comment in Bug 463510.






From:      
 David M Williams/Raleigh/IBM@IBMUS
To:      
 orbit-dev@xxxxxxxxxxx,

Date:      
 04/13/2015 01:10 AM
Subject:    
   Re: [orbit-dev]
Declaring Build: I20150412191215 - build improved.
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

With this build, the build has been
changed to use Java 8 tools when it does pack200, to match the tools used
by Eclipse Foundation's "batch signing service". (See bug 464100)

BUT, 

So far that has not been applied to much since we use the "mirror
with comparator" method to re-use bundles that have not changed (since
the last release). Some testing implies that some of those "old bundles"
might have to be not-packed, if we ever had to change them, but I hope
to find time to put in an automatic "verify" test for each build,
so we'll know right away when that is the case. 

And, that's not to say there might be some reason to change a lot of the
old bundles (to correct names, to make signing certificate current, etc.)
but, we'll treat that separately. 

Also, while doing this work, I've learned how important it is for consumers
to not "re-sign" or "re-pack" any bundles they get
from Orbit, but they should use the jar file, and *jar.pack.gz file (if
it exists) "as is". I'm assuming most of the builders do this
automatically, but, do not know details. (I know that PDE builds do not
do it automatically and anything that is not to be re-signed, re-conditioned,
etc., must be explicitly excluded from what is sent to the batch signing
service). 

Just wanted to be clear the Orbit builds were "open for business"
and M7 isn't that far off! 

Thanks, 





From:        David
M Williams/Raleigh/IBM@IBMUS 
To:        orbit-dev@xxxxxxxxxxx,
Date:        04/12/2015
10:06 PM 
Subject:        [orbit-dev]
Declaring Build: I20150412191215 
Sent by:        orbit-dev-bounces@xxxxxxxxxxx

---

Download Page:
http://download.eclipse.org//tools/orbit/downloads/drops/I20150412191215

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev