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

Bug 154085

Summary:	OSGi R4.1 Specification Work
Product:	[Eclipse Project] Equinox	Reporter:	John Arthorne <john.arthorne>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	alex.blewitt, bpasero, caniszczyk, dev, gorkem.ercan, jin.phd, Joel.Kamentz, pascal, simon_kaegi, wayne.beaton
Version:	3.3	Keywords:	plan
Target Milestone:	3.3 M5
Hardware:	All
OS:	All
Whiteboard:

Description John Arthorne

2006-08-16 12:22:07 EDT

Much of the success Eclipse has enjoyed with OSGi comes from the fact that the    Eclipse community has played a very active role in the evolution of various OSGi specifications.  With increased interest in OSGi and Java modularity (see JSR 277, JSR 291 and JSR 232) this participation has never been more important. In addition to promoting Eclipse use-cases and the evolution of these standards to benefit Eclipse, there are a number of gaps in the OSGi specifications that Eclipse is currently filling in specific ways and should be addressed in R5. For example the management of API in metadata (x-friends and x-internal), integration techniques for third party and legacy code, in-place execution of    bundles, basic notions of data location, etc.  The Equinox team will continue    their active participation in these specification processes and keep Eclipse on the leading edge of Java componentization.

Comment 1 DJ Houghton

2007-02-21 14:28:45 EST

Original Summary: OSGi R5 Specification Work

Note that originally this plan item targeted R5 but the next version of the spec is going to be R4.1 so we have updated this item accordingly.

Comment 2 Thomas Watson

2007-03-16 17:48:50 EDT

This was done in M5.  The OSGi alliance is currently using M5eh for the reference implementation of R4.1.