Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 136625

Summary: GEF runtime jars should be signed
Product: [Tools] GEF Reporter: Randy Hudson <hudsonr>
Component: GEF-Legacy GEF (MVC)Assignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: 3.3.0 (Europa) M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Randy Hudson CLA 2006-04-13 09:44:09 EDT 
Not sure what the priority is on this, as the platform has just recently decided to slip it in. Just thought we should track it.
Comment 1 Steven R. Shaw CLA 2006-05-05 10:19:43 EDT 
Is there any additional info on this task?
Comment 2 David Williams CLA 2006-05-05 11:08:26 EDT 
I believe since this was open, the platform has decided not to sign jars, since can have some unanticipated performance penalties .. so they felt to "risky" to do at this point. They have, I believe, prepared they build process that it could be easily added later. So, there might be work that could be done here, but I do not think anything concrete for this year.
Comment 3 Anthony Hunter CLA 2006-11-02 14:54:17 EST 
This is supposed to be a requirement for Europa (3.3 simultaneous release).

See Bug 135044
Comment 4 Anthony Hunter CLA 2007-03-21 07:40:09 EDT 
I have done the process to get the JAR Signing privileges through the Eclipse foundation.

A few tweaks needed to be done on build.eclipse.org and with the help of the eclipse webmaster I have signed the 3.3 M5 build.

I will close in 3.3 M6
Comment 5 Anthony Hunter CLA 2007-03-30 09:11:27 EDT 
Closing this task as accomplished since I ran the Eclipse jar signer on M6.

Raised Bug 180188 as for whatever reason some GEF 3.3 M6 jars are not signed.