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

Bug 377143

Summary:

[Nested UML Compare] Comparison between 2 elements which have the same name is not correct

Product:

[Modeling] Papyrus

Reporter:

Vincent Lorenzo <vincent.lorenzo>

Component:

Core

Assignee:

Vincent Lorenzo <vincent.lorenzo>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

0.9.0

Target Milestone:

Hardware:

All

OS:

All

Whiteboard:

Bug Depends on:

Bug Blocks:

371606

Attachments:

Description	Flags
This image illustrates the problem	none

Description Vincent Lorenzo

2012-04-19 02:34:01 EDT

Steps to reproduce : 
	- Create a new model
	- Create 2 classes in this model (Class1 and Class2)
	- Compare the class with each other
		-> 2 differences are found (instead of 1) : 
			- "name has changed" -> OK
			- Class1 has been moved from null to null -> should not be here

Comment 1 Vincent Lorenzo

2012-04-19 02:35:47 EDT

Created attachment 214219 [details]
This image illustrates the problem

Comment 2 Vincent Lorenzo

2012-04-19 02:40:32 EDT

In R7927 : share an example of this problem in sandbox/NestedCompare
plugin name : NestedCompare_ChangeNameExample

Comment 3 Vincent Lorenzo

2012-04-19 02:43:31 EDT

FYI, in the difference viewer, the line  "Class1 has been moved from null to null" is MoveModelElement

Comment 4 Vincent Lorenzo

2012-04-19 03:05:02 EDT

Corrected in R7929. This bug can be closed.