Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 396267 - [UML Compare] it is not possible to merge a difference on a stereotype property
Summary: [UML Compare] it is not possible to merge a difference on a stereotype property
Status: CLOSED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M7   Edit
Assignee: Vincent Lorenzo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 330183
  Show dependency tree
 
Reported: 2012-12-11 07:34 EST by Vincent Lorenzo CLA
Modified: 2012-12-11 08:03 EST (History)
2 users (show)

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 Vincent Lorenzo CLA 2012-12-11 07:34:41 EST 
Steps to reproduce : 
	1/Create a model with an applied profile and a stereotype application which contains properties
	2/ Save As this model and change the value of the property of the stereotype
	3/ Compare these 2 models
	4/ Select the difference -> a dialog with the follonwing message is open : Thefeature 'name of the property' is not a valid feature
Comment 1 Vincent Lorenzo CLA 2012-12-11 08:03:20 EST 
Corrected on branch and trunk in R9618. I didn't identify the change which provided this exception. 
The problems came from the call to the toString method on DiffElement. When we are comparing difference on a stereotype property, the toString try to find the stereotype property (the feature) in the stereotyped element... that's why it is not a valid feature. 
	-> I correct the call to the toString method

	This bug can be marked as closed fixed.