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

Bug 113663

Summary:	[plan item] Refactor the runtime.
Product:	[Eclipse Project] Equinox	Reporter:	Mike Wilson <Mike_Wilson>
Component:	Compendium	Assignee:	equinox.compendium-inbox <equinox.compendium-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	ed.burnette, gunnar, mlists, morten-eclipse, ob1.eclipse, patmc, pombredanne, simon_kaegi, tjwatson
Version:	3.1	Keywords:	plan
Target Milestone:	3.2
Hardware:	All
OS:	All
Whiteboard:

Description Mike Wilson

2005-10-25 10:14:12 EDT

The Eclipse runtime is currently one monolithic plugin that contains the extension registry, jobs, 
preferences, content types, application model and various helper/utility classes.  Various use cases 
demand independent use of these faciliities.  The runtime should be refactored into individual bundles for 
the different functional areas to improve the support for specific use cases such as using the extension 
registy on standard OSGi systems or standalone and better integration between the Eclipse application 
model and OSGi (e.g., the OSGi MEG application model). [Framework, Bundles, Platform Runtime]

Comment 1 Thomas Watson

2005-10-25 10:28:20 EDT

See bug 109893 which invesigates using the MEG Application Admin model for 
Eclipse applications.

Comment 2 Thomas Watson

2005-12-13 16:48:21 EST

Moving to bundles, but I'm pretty sure this bug can be closed for M4 since the major work has already been done to split the runtime.

Comment 3 Jeff McAffer

2006-01-12 23:09:21 EST

there are still several things that need to be investigated/completed.  In particular, the positioning of Platform, code reviews, dealing with the AuthorizationDatabase code, deprecations, API, ...

Comment 4 Thomas Watson

2006-02-16 13:59:55 EST

No longer doing MEG app admin stuff for 3.2.

Comment 5 Pascal Rapicault

2006-04-05 09:48:15 EDT

This bug has been fixed. Since M4 the runtime is now split into:
- equinox.common
- equinox.registry
- equinox.preferences
- core.jobs (the jobs API)
- core.runtime.regsitry.compatibility (compatibility layer for the registry)

For more details about the equinox bundle see  http://www.eclipse.org/equinox/bundles/

The split of the authorization code is covered in another bug report and should be addressed in RC1.