Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341222 - customization on feature defined in another metamodel
Summary: customization on feature defined in another metamodel
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EMF-Facet (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-29 08:34 EDT by Nicolas Bros CLA
Modified: 2020-05-01 11:26 EDT (History)
2 users (show)

See Also:
nicolas.bros: 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 Nicolas Bros CLA 2011-03-29 08:34:51 EDT 
If I define a customization on EModelElement#eAnnotations from the ecore metamodel and set appliesToSubclasses to true, the customization for eAnnotations doesn't work on metaclasses that are subtypes of EModelElement but are not defined in the ecore metamodel.
Comment 1 Nicolas Bros CLA 2011-03-29 10:00:12 EDT 
Fixed in revision 466.
Comment 2 Nicolas Bros CLA 2011-03-29 10:03:13 EDT 
To register a metamodel on which customizations may be applied even if the customization is not defined on it, call CustomizationEngine#registerMetamodel with the URI of the metamodel to register.
Comment 3 Gregoire Dupe CLA 2011-03-30 09:13:49 EDT 
This bug can be closed.