Jump to: navigation, search

Difference between revisions of "EMF DiffMerge"

(New page: == Introduction == EMF Diff/Merge provides a lightweight, versatile engine for comparing and merging models using IDs. *The emphasis is on scalability and reliability so that large mod...)
 
Line 6: Line 6:
 
*The scope is 2-way and 3-way comparison and matching by ID, where an ID can be any "signature" that uniquely identifies an element within its scope (Ecore ID, XML ID, qualified name, location in model tree, etc.).  
 
*The scope is 2-way and 3-way comparison and matching by ID, where an ID can be any "signature" that uniquely identifies an 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 full-fledged&nbsp;enabler for multiple usages: version control, incremental model transformations, model refactoring, etc.<br>
+
*The final goal is to have a full-fledged&nbsp;enabler for multiple usages: version control, incremental model transformations, model refactoring, etc.
 +
 
 +
 
 +
 
 +
== Resources ==
 +
 
 +
*[http://www.eclipse.org/forums/index.php?t=thread&frm_id=246 Forum]: a forum for discussions about the project
 +
*[http://www.eclipse.org/projects/project.php?id=modeling.emf.diffmerge Project summary]: a summary of the current state of the project
 +
*[http://www.eclipse.org/proposals/modeling.emf.edm/ Project proposal]: the original proposal that led to the creation of the project

Revision as of 05:13, 23 July 2012

Introduction

EMF Diff/Merge provides a lightweight, versatile 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 and matching by ID, where an ID can be any "signature" that uniquely identifies an 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 full-fledged enabler for multiple usages: version control, incremental model transformations, model refactoring, etc.


Resources

  • Forum: a forum for discussions about the project
  • Project summary: a summary of the current state of the project
  • Project proposal: the original proposal that led to the creation of the project