Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EMF DiffMerge"
Line 4: | Line 4: | ||
*The emphasis is on scalability and reliability so that large models can be merged consistently. | *The emphasis is on scalability and reliability so that large models can be merged consistently. | ||
− | *The scope is 2-way and 3-way comparison | + | *The scope is 2-way and 3-way comparison of arbitrary EMF models. Model elements (''EObject'') 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 GUI with reusable UI components is also included. | ||
*The final goal is to have a mature, versatile building block for multiple usages: version control, incremental model transformations, model refactoring, etc. | *The final goal is to have a mature, versatile building block for multiple usages: version control, incremental model transformations, model refactoring, etc. | ||
+ | |||
+ | |||
The EMF Diff/Merge project is part of [http://www.eclipse.org/projects/project.php?id=modeling.emf EMF]. | The EMF Diff/Merge project is part of [http://www.eclipse.org/projects/project.php?id=modeling.emf EMF]. | ||
Line 12: | Line 14: | ||
<br> | <br> | ||
− | == Usage == | + | == Usage == |
− | *[http://wiki.eclipse.org/EMF_DiffMerge/Programmatic_Usage Programmatic usage and concepts] | + | *[http://wiki.eclipse.org/EMF_DiffMerge/Programmatic_Usage Programmatic usage and concepts] |
*[http://wiki.eclipse.org/EMF_DiffMerge/Default_GUI Default GUI] | *[http://wiki.eclipse.org/EMF_DiffMerge/Default_GUI Default GUI] | ||
− | + | <br> | |
== Links<br> == | == Links<br> == |
Revision as of 09:58, 24 July 2012
Introduction
EMF Diff/Merge provides a lightweight engine for comparing and merging models using IDs.
- The emphasis is on scalability and reliability so that large models can be merged consistently.
- The scope is 2-way and 3-way comparison of arbitrary EMF models. Model elements (EObject) 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.
- The final goal is to have 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