Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 384490 - [UML Compare] Comparison between stereotyped elements doesn't work in the nested Compare Editor
Summary: [UML Compare] Comparison between stereotyped elements doesn't work in the nes...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M7   Edit
Assignee: Vincent Lorenzo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 383880
  Show dependency tree
 
Reported: 2012-07-06 11:38 EDT by Vincent Lorenzo CLA
Modified: 2014-03-26 05:14 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2012-07-06 11:38:00 EDT
Steps to reproduce : 
	1/ create a model with 2 classes stereotyped block
	2/ set the attribute isEncapsulated to true for 1 of the blocks
	3/ compare the 2 classes
		-> no differences found
Comment 1 Vincent Lorenzo CLA 2012-07-24 04:23:05 EDT
R8616 : commit the example for the JUnit test for the StereotypeApplicationAddition/Removal
Comment 2 Vincent Lorenzo CLA 2012-07-25 09:44:36 EDT
To complete this bug, the difference between a stereotyped element and a no stereotyped element is not found.

R8619 : a first commit to correct this bug + JUnit tests
	Manage only the StereotypeApplicationAddition/Removal
	in some case, it doesn't work yet.
Comment 3 Vincent Lorenzo CLA 2012-07-25 09:59:18 EDT
R8622 : 
Commit 2 examples to tests differences on stereotype application.
These 2 examples don't work properly (they are not corrected by the previous commit)
Comment 4 Vincent Lorenzo CLA 2013-02-06 09:43:22 EST
R10071 : corrected on branch (plugin oep.uml.compare.diff)
R10072 : corrected in trunk (plugin oep.uml.compare.diff)
R10073 : minor changes in oep.uml.compare.subelement required by the previous commit.

I don't close the bug because we must provide JUnit test for this feature
Comment 5 Vincent Lorenzo CLA 2013-02-06 12:03:30 EST
R10074(branch) and 10075 (trunk) add a for to cross all required strereotype application (and not only on the first level of comparison)
Comment 6 Toni Siljamäki CLA 2013-10-10 07:49:40 EDT
Are all the [UML Compare] bugs really valid, wrt EMF Compare?
Comment 7 Camille Letavernier CLA 2014-03-26 05:14:54 EDT
> Are all the [UML Compare] bugs really valid, wrt EMF Compare?

Most of them are not valid anymore

I close this task