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

Bug 365744

Summary: [EFacet] Customization and Facet can't be declared on EObject and used on another emf metamodel (UML, gmf.Notation, ...)
Product: z_Archived Reporter: Vincent Lorenzo <vincent.lorenzo>
Component: EMF-FacetAssignee: Project Inbox <emft.facet-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P5 CC: gdupe
Version: unspecifiedFlags: gdupe: juno+
gdupe: kepler+
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 365714, 380230, 380450    

Description Vincent Lorenzo CLA 2011-12-06 09:41:26 EST 
I think there is an inconsistency between the Table and the ModelExplorer used in Papyrus. In the ModelExplorer, we use the CustomizationManager, whereas in the NattableWidget, this object is not used, the widget manages itself the CustomizationEngine.
So, in the table we can use customizations declared on EObject (often used to hide the eAnnotation columns), but in the ModelExplorer (we use org.eclipse.emf.facet.infra.browser.uicore.CustomizableModelLabelProvider), we can't use Customization for color, italic, ... declared on EObject (the same problem with the facet).
Comment 1 Vincent Lorenzo CLA 2012-02-20 03:36:56 EST 
Could you integrate this requirement to your new EMF-Facet version?
Comment 2 Gregoire Dupe CLA 2012-02-20 04:51:00 EST 
Yes, it must.