Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EMF Compare/Specifications/FeatureMap"

(Evolution Specification: handling of FetaureMaps in EMF Compare)
(Evolution Specification: handling of FetaureMaps in EMF Compare)
Line 8: Line 8:
  
 
== Introduction  ==
 
== Introduction  ==
 
  
 
The following metamodel will be use for the specification.
 
The following metamodel will be use for the specification.
 +
 +
[[file:EMFCompare_FeatureMaps_MM.png]]
  
 
== Detailed Specification  ==
 
== Detailed Specification  ==

Revision as of 04:37, 15 April 2014

Evolution Specification: handling of FetaureMaps in EMF Compare

Current status is DRAFT

Preamble

Summary: Define how to graphically represent feature maps changes.

Introduction

The following metamodel will be use for the specification.

File:EMFCompare FeatureMaps MM.png

Detailed Specification

Addition/deletion of a value for a given key

Solution 1: 2 differences, 1 refinement

In the structure merge viewer:

  • 1 difference on the orders : EFeatureMapEntry attribute
  • 1 difference on the standardOrders/priorityOrders reference
  • 1 refinement of the previous differences (the reference change is the prime refining), with a new FeatureMap filter
  • the merge of a diff implies the merge of the other diff.

In the content merge viewer:

  • For the difference on the orders : EFeatureMapEntry reference: table merge viewer
  • For the standardOrders/priorityOrders reference: tree merge viewer

Solution 2: 1 difference

In the structure merge viewer:

  • 1 new type of difference: FeatureMapChange

In the content merge viewer:

  • For the standardOrders/priorityOrders reference: tree merge viewer

Key change for a given value

Solution 1: table merge viewer

In the structure merge viewer:

  • 1 new type of difference on the the standardOrders/priorityOrders references: FeatureMapChange

In the content merge viewer:

  • table merge viewer

Solution 2: new merge viewer

In the structure merge viewer:

  • 1 new type of difference on the the standardOrders/priorityOrders references: FeatureMapChange

In the content merge viewer:

  • new merge viewer: FeatureMapMergeViewer

Back to the top