Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355159 - StandaloneSetup: add possibility to map bundle names
Summary: StandaloneSetup: add possibility to map bundle names
Status: RESOLVED FIXED
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: 1.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: SR2   Edit
Assignee: Karsten Thoms CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-18 15:37 EDT by Karsten Thoms CLA
Modified: 2011-08-18 16:21 EDT (History)
1 user (show)

See Also:
karsten.thoms: indigo+

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 Karsten Thoms CLA 2011-08-18 15:37:39 EDT 
StandaloneSetup scans for .project files and registers the bundle symbolic name as in the platform resource map.

However, in some cases it might not be true that the directory name equals the bundle name. In this case it must be possible to map the bundle name to a the directory name and add this path also in the platform resource map.
Comment 1 Sebastian Zarnekow CLA 2011-08-18 15:41:57 EDT 
It should already work to register a uri mapping from

platform:/resource/wrong.project.name
to
platform:/resource/fixed.project.name
Comment 2 Karsten Thoms CLA 2011-08-18 16:16:14 EDT 
No, this did now work. In this case I got several "The path ... is unmapped" when generating an Xtext DSL. Mapping each single URI is not feasible in this case.
Comment 3 Karsten Thoms CLA 2011-08-18 16:21:16 EDT 
Added method 'addBundleMap(Mapping)' and registering the mapped bundle name in registerProject().