Eclipse Community Forums: Compare » Problems using the UI compare with dynamic Ecore models

Home » Modeling » Compare » Problems using the UI compare with dynamic Ecore models

Problems using the UI compare with dynamic Ecore models [message #1752819]

Fri, 27 January 2017 11:24

Eclipse User

Hi,

Im facing a problem using the UI of EMF Compare with the instances (.xmi files) of a dynamic Ecore model.

Im using the bank example of EMF Henshin provided here: http://git.eclipse.org/c/henshin/org.eclipse.emft.henshin.git/tree/plugins/org.eclipse.emf.henshin.examples/src/org/eclipse/emf/henshin/examples/bank
When I try to compare example-bank.xmi with example-result.xmi I get problems reported regarding an EClass in the dynamic Ecore model.
I already update my EMF compare version from 3.2.1 to latest version 3.3.0 in hope of an already fixed bug. I also couldn't find information on special issues regarding dynamic ecore models.

Is this already reported as a bug or shall I do so?

Best regards, Kris

index.php/fa/28246/0/

Attachment: EMF Compare bug.JPG
(Size: 198.34KB, Downloaded 649 times)

Re: Problems using the UI compare with dynamic Ecore models [message #1752880 is a reply to message #1752819]

Mon, 30 January 2017 04:13

Eclipse User

Hi Kristopher,

please feel free to report a bug with the example models. I haven't used EMF Compare with dynamic models for quite a while. It looks like the metamodel cannot be resolved even though in the models you linked in the Henshin git repo, the schema location seems to be correct. You could also try to register the metamodel in the package registry before the comparison.

Best wishes,

Philip

--
Philip Langer

Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/

Re: Problems using the UI compare with dynamic Ecore models [message #1753176 is a reply to message #1752880]

Thu, 02 February 2017 08:04

Eclipse User

Hello Philip,
thank you for the quick response.

To register the metamodel in the package registry could be a temporary workaround, but I think that shouldn't be an overall solution. I'm afraid that this could lead to a clash when another variant of the metamodel is already installed.
I've opened a bug on this behaviour, see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=511549

Best regards, Kristopher

Previous Topic:	Using a custom merger
Next Topic:	Compare models structurally equal

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Aug 05 09:25:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter