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

Bug 322046

Summary:	Support standalone 'plugin.xml' initialization
Product:	[Modeling] EMF	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	Ed Merks <Ed.Merks>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.6.0
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Ed Willink

2010-08-07 07:30:32 EDT

A variety of plugin extension points in EMF and related projects provide extensible configuration when Eclipse is running.

EMF and related projects endeavour to provide standalone operation as well, but this requires a Java paraphrase of plugin.xml sometimes facilitated by an initialization helper routine. Any errors in this initialization cause users considerable difficulties. For instance, getting a UML genmodel to work from a CMOF package merge within MWE is not easy. Getting OCL delegates to work standalone is also not easy.

Many EMF extension points have very similar 'put-a-class-in-a-keyed-registry' behaviour. Many others could be revised to adopt a shared registration.

With e4 revamping plugin configuration and using EMF, perhaps this could be a good time to define a factory registration API to ensure that the revamped plugin registrations are re-useable standalone.

Comment 1 Ed Merks

2010-08-07 11:43:48 EDT

I'm really not sure why MWE doesn't support an OSGi mode, but that's a whole other discussion.  I'm also not keen in inventing a parallel mechanism when there is already a perfect good mechanism, i.e., we can just reuse what's already there with the contributions in https://bugs.eclipse.org/bugs/show_bug.cgi?id=271253.

*** This bug has been marked as a duplicate of bug 271253 ***

Comment 2 Ed Willink

2010-08-07 12:01:09 EDT

I'm pleased that an approach for this is under active consideration.

Bug 309003 requests an OSGI mode for MWE.