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

Bug 425030

Summary: Extension processor only works on Windows platform
Product: [Modeling] EMF Reporter: Christian Damus <give.a.damus>
Component: CoreAssignee: Ed Merks <Ed.Merks>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 2.10.0   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X   
Whiteboard:
Bug Depends on:    
Bug Blocks: 401804    

Description Christian Damus CLA 2014-01-07 11:07:45 EST
EMF Core 2.10 as of commit b86b9a8 (Dec. 18 2013)

The EcorePlugin.ExtensionProcessor is very convenient for loading plugin.xml extensions in a non-Eclipse deployment.  However, its method of scanning the classpath for plugin.xml resources by parsing the java.class.path system property only works on Windows.  This property uses the ";" separator only on that platform.  The parsing should split on the value of the "path.separator" system property.
Comment 1 Christian Damus CLA 2014-01-07 11:15:36 EST
This bug blocks the implementation of extension-processor support in UML2 (bug 401804).

I have pushed a Gerrit review that works for UML2 in stand-alone mode on Mac platform (at least):

https://git.eclipse.org/r/20339
Comment 2 Kenn Hussey CLA 2014-01-09 17:01:53 EST
Ed, any chance Christian's fix could be reviewed/committed and included in an upcoming integration build?
Comment 3 Ed Merks CLA 2014-01-13 07:54:23 EST
Rather than using system properties, I've used File.pathSeparator.  The change is committed to master.

http://git.eclipse.org/c/emf/org.eclipse.emf.git/commit/?id=a9b542dd9ebfbc22173df62b047b46510047fad6
Comment 4 Kenn Hussey CLA 2014-01-13 10:02:28 EST
Thanks, Ed!
Comment 5 Ed Merks CLA 2014-06-21 02:19:53 EDT
The changes are available in the latest release.