Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316740 - [Profile] Deleting an element doesn't delete its stereotypes
Summary: [Profile] Deleting an element doesn't delete its stereotypes
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.7.0   Edit
Assignee: Thibault Landré CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 06:20 EDT by Thibault Landré CLA
Modified: 2010-06-27 17:58 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 Thibault Landré CLA 2010-06-14 06:20:35 EDT 
When deleting an element with applied stereotypes, the element is correctly deleted but its stereotypes remain. 

They should also be deleted.
Comment 1 Thibault Landré CLA 2010-06-14 09:42:27 EDT 
Add a new command which will delete the stereotype application associated when deleting the uml element.
Comment 2 Yann Tanguy CLA 2010-06-27 17:58:32 EDT 
Generated code should not be modified manually: change code generation instead.

The gmfgenextension is extended with a new item (AdditionalEditPartCandies extending gmfgen EditPartCandies item) which allows to specify a specific java package for the BaseEditHelper used by generated classes. The same BaseEditHelper can then be put in oep.diagram.common modified and used by any diagram.
In such a case the BaseEditHelper in the generated code becomes unused (still generated because avoiding generation would require to change gmf default code generator).

If no AdditionalEditPartCandies is specified, the code is generated normally.

A BaseEditHelper taken care of unapplying stereotypes before deletion has been put in oep.diagram.common.helper.UMLBaseEditHelper.

(Done in r2104)