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

Bug 366411

Summary: Palette configurations are separately de/activatable when deployed in the same bundle
Product: [Modeling] Papyrus Reporter: Marc-Florian Wendland <marc-florian.wendland>
Component: CoreAssignee: Project Inbox <mdt-papyrus-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 0.8.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Marc-Florian Wendland CLA 2011-12-12 09:29:34 EST 
When several palette configurations are deployed in the very same bundle, they cannot be separately activated or deactivated. When de-/activating one palette configuration, all palette configurations of the bundle are de-/activated together.

This is not very inconvenient, since it requires developers to extract each palette configuration into a separate bundle, although the architecture of the extension point copes with defining several isolated palette configuration in one single bundle.
Comment 1 Camille Letavernier CLA 2012-01-03 07:49:46 EST 
This is the same problem as reported in Bug 348352 (Although this is more generic)

*** This bug has been marked as a duplicate of bug 348352 ***