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

Bug 316740

Summary:	[Profile] Deleting an element doesn't delete its stereotypes
Product:	[Modeling] Papyrus	Reporter:	Thibault Landré <thibault.landre>
Component:	Core	Assignee:	Thibault Landré <thibault.landre>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.7.0
Target Milestone:	0.7.0
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Thibault Landré

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é

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

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)