Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EMF DiffMerge"
| Line 3: | Line 3: | ||
EMF Diff/Merge provides a lightweight engine for comparing and merging models using IDs. | EMF Diff/Merge provides a lightweight engine for comparing and merging models using IDs. | ||
| − | *The scope is 2-way and 3-way comparison of arbitrary EMF models (or "instance models"). | + | *The scope is 2-way and 3-way comparison of arbitrary EMF models (or "instance models"). |
*Model elements are matched by ID, where an ID can be any "signature" that uniquely identifies the element within its scope: Ecore ID, XML ID, qualified name, location in model tree, etc. | *Model elements are matched by ID, where an ID can be any "signature" that uniquely identifies the element within its scope: Ecore ID, XML ID, qualified name, location in model tree, etc. | ||
| − | *A GUI with reusable UI components is also included. | + | *A dedicated GUI with reusable UI components is also included. |
| − | Besides, the tool is intended to satisfy the following requirements. | + | Besides, the tool is intended to satisfy the following requirements. |
| − | It must support the comparison and merge of large models. There is thus an emphasis on scalability and reliability. | + | *It must support the comparison and merge of large models. There is thus an emphasis on scalability and reliability. |
| + | *The order in which differences are merged must have no impact. | ||
The final goal is to obtain a mature, versatile building block for multiple usages: version control, incremental model transformations, model refactoring, etc.<br> | The final goal is to obtain a mature, versatile building block for multiple usages: version control, incremental model transformations, model refactoring, etc.<br> | ||
Revision as of 10:09, 24 July 2012
Introduction
EMF Diff/Merge provides a lightweight engine for comparing and merging models using IDs.
- The scope is 2-way and 3-way comparison of arbitrary EMF models (or "instance models").
- Model elements are matched by ID, where an ID can be any "signature" that uniquely identifies the element within its scope: Ecore ID, XML ID, qualified name, location in model tree, etc.
- A dedicated GUI with reusable UI components is also included.
Besides, the tool is intended to satisfy the following requirements.
- It must support the comparison and merge of large models. There is thus an emphasis on scalability and reliability.
- The order in which differences are merged must have no impact.
The final goal is to obtain a mature, versatile building block for multiple usages: version control, incremental model transformations, model refactoring, etc.
The EMF Diff/Merge project is part of EMF.
Usage
Links
- Project summary: a summary of the current state of the project
- Project proposal: the original proposal that led to the creation of the project
- Forum: the dedicated newsgroup
- Bugzilla: for reporting bugs