Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354575 - StandaloneSetup.scanClassPath does not configure platform:/plugin
Summary: StandaloneSetup.scanClassPath does not configure platform:/plugin
Status: NEW
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-12 01:00 EDT by Ed Willink CLA
Modified: 2011-08-12 01:14 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-08-12 01:00:31 EDT 
When building an Xtext editor that uses JVM types, the corresponding manual genmodel may refer to

    usedGenPackages="platform:/plugin/org.eclipse.xtext.common.types/model/JavaVMTypes.genmodel#//types"

which requires help to resolve outside Eclipse.

StandaloneSetup.scanClassPath may be used to install plugins as platform:/resource, but a uriMap must be added to make the platform:/plugin name work.

[This may be because the corresponding EcorePlugin code requires a non-null workspaceRoot.] I guess that MWE needs to just install both names.
Comment 1 Ed Willink CLA 2011-08-12 01:14:09 EDT 
NB. platform:/plugin rather than platform:/resource is the EMF way to refer to models expected to be in plugins. See UML.genmodel, UML.ecore, OCLEcore.genmodel or OCL.ecore all of which emanate from the original IBM teams.