Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EMF Compare/Roadmap"

 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Plan =
+
= Overall Goal =
== Long Term ==
+
EMF Compare's focus is on providing a powerful, stable and proven framework for model comparison and merging. The API should be usable
+
in any context from the plain Java application to the complete IDE customization.
+
  
=== Framework Enhancements ===
+
EMF Compare's focus is on providing a powerful, stable and proven framework for model comparison and merging. The API should be usable in any context from the plain Java application to the complete IDE customization.  
==== per namespace MatchEngine selection and dynamic switching ===
+
Right now EMF compare allows adopters to define specific match or diff engines associated with file extensions.  As EMF is more and more
+
broadly used we often encounter cases where a given file contains model elements conformed to several Ecore models.
+
  
A MatchEngine (and respectively Diff Engine) should be associated with one or several EPackages and not with the serialization mechanism. Furthermore
+
= Plan  =
that would require the Match process in general to be able to switch from a MatchEngine to another depending on the elements it is matching.
+
  
 +
== Short Term ==
 +
== Mid-Term  ==
 +
== Short Term  ==
  
=== 2 ways and 3 ways merge robustness ====
+
=Release Schedule=
We have a bunch of issues reported by the adopters about the merge support, we need to work on building a strong test basis to make sure the merge is perfect in any kind of scenarios for instance fragmented models, scoped matching ...
+
  
=== High Performances during matching phase ===
+
<googlecalendar width="100%" title="Schedule">gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com</googlecalendar>
The matching phase is critical for performances, several optimization could be done (some being addressed by the Google Summer of Code 2010).
+
  
=== Match/Diff/Merge on elements not contained in a EMF Resource ===
+
The calendar is available in the following formats:
The framework can be used on any kind of EObjects, but as historically it was about providing model comparison support for file based models many parts of the code are making assumptions about a resource being there or not.
+
[http://www.google.com/calendar/ical/gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com/public/basic.ics ICal], [http://www.google.com/calendar/feeds/gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com/public/basic ATOM News Feed], [http://www.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com HTML]
  
We should build a strong test basis with eObjects not being in resources, being compared and merged.
+
[[Category:EMF_Compare]]
 
+
* MatchModel maintenance on incremental changes
+
 
+
 
+
* DiffModel maintenance on incremental changes
+
* Re-Usable Comparison UI Component
+
* Undo/Redo support in comparison editor
+
* ChangeModel to DiffModel and DiffModel to ChangeModel
+
 
+
=== Tooling Enhancements ===
+
* Integration with the Team Model Synchronization UI
+
* Generating a Custom Match Engine from Ecore Annotations.
+
 
+
 
+
== 2011 ==
+
 
+
 
+
* [[EMF Compare 1.2.0 New And Noteworthy | New and Noteworthy : 1.2.0]]
+
 
+
== 2012 ==
+
 
+
== 2013 ==
+
 
+
= Released bits =
+
== 2010 ==
+
* [[EMF Compare 1.1.0 New And Noteworthy | New and Noteworthy : 1.1.0]]
+
== 2009 ==
+
* [[EMF Compare 1.0.0 New And Noteworthy | New and Noteworthy : 1.0.0]]
+
== 2008 ==
+
* [[EMF Compare 0.8.0 New And Noteworthy | New and Noteworthy : 0.8.0]]
+
 
+
* Initial project description : [[Media:EMFCompareDescription.pdf | EMF Compare Description (PDF)]]
+

Latest revision as of 08:20, 6 October 2014

Overall Goal

EMF Compare's focus is on providing a powerful, stable and proven framework for model comparison and merging. The API should be usable in any context from the plain Java application to the complete IDE customization.

Plan

Short Term

Mid-Term

Short Term

Release Schedule

The calendar is available in the following formats: ICal, ATOM News Feed, HTML

Back to the top