Hello Aleksandar,
Nevertheless, here are a couple of answers.
- Consistency rules are a mechanism that allows you to merge differences without breaking your models. You do not need to worry about what they do, unless your metamodel implementation manifests very specific behavior, i.e., you have redefined the default getter/setter operations generated by EMF. Simply compare models and ask the tool to merge a subset of the differences, and the tool takes care of the rest.
- The focus of EMF Diff/Merge is on merging models. You can use it for comparison as well, since comparison is a prerequisite to merging, but you need to provide a criterion for matching Ecore elements since they do not have IDs. This can be defined in a match policy (IMatchPolicy) – check the wiki if you want to know how. You can then experiment and see if the output of the tool suits your needs by selecting any couple of (meta-)model files and clicking “Compare with à Each other as models”.
Hope it helps.
Cheers,
Olivier
Hello,
is the EMF Diff/Merge based on EMF Compare? If yes, what are the benefits using the EMF Diff/Merge? I saw the proposal page and it is described that the both projects are complementary and "EDM operates at a lower level of abstraction: its difference model is technical so as to support the _expression_ of consistency rules". Can you give me some examples how can the consistency rules be used and what are they for?
At the moment I'm using the EMF Compare to compute the difference of two metamodels. After that I want to analyze the Diffs in order to see if the changes are significant and if the models have to be transformed to the new metamodel. Would EMF Diff/Merge give me more benefits?
