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

Bug 263363

Summary:	Signing
Product:	z_Archived	Reporter:	Bjorn Freeman-Benson <bjorn.freeman-benson>
Component:	Eclipselink	Assignee:	Nobody - feel free to take it <nobody>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	douglas.clarke, peter.krogh
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	252799

Description Bjorn Freeman-Benson

2009-02-02 20:14:09 EST

+++ This bug was initially created as a clone of Bug #252799 +++

Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons.

Comment 1 Eric Gwin

2009-04-14 12:48:36 EDT

Need to look at several factors:
- Seems to require a UI (add to help). Not certain if feasible.
- May cause a performance regression, is this required for runtime components?

Comment 2 Peter Krogh

2009-05-05 10:15:51 EDT

We will be shipping signed bundles.

We are putting this in place.

Comment 3 Eric Gwin

2009-05-20 14:30:36 EDT

Completed changes to our process last Friday for an end-to-end automated signing solution.

It's looking like I'll need to make some adjustments to compensate for some signing side-effects (not sign some non-galileo jars), but process is complete.

closing.

Comment 4 Eclipse Webmaster

2022-06-09 10:21:15 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink