Skip to main content
Jump to: navigation, search

Difference between revisions of "Profile migration"

(Created page with "=Description= For now Papyrus provide a static migration base on modification of the profile. However, in some case this static migration could be problematic for instance it...")
 
Line 1: Line 1:
=Description=
+
=Context=
For now Papyrus provide a static migration base on modification of the profile. However, in some case this static migration could be problematic for instance it could delete a stereotype while we just want to replace it by an other one and reuse some attribute values.
+
When a profile change we have to reapply it in all models whose apply it. This action of simply reapply this profile could lose some information and the model can become invalid.
 +
 
 +
=Proposition=
 +
A new tool which will allow to migrate a profiled model when the profile evolve. This means that it will reapply the profile and ask the user some action to modify the model according to the modification of the profile. For example, if a stereotype becomes abstract then we will ask the designer if he wants to replace the abstract stereotype by a specification of this stereotype.
 +
 
 +
=Actions to tackle=
 +
* Compare profile before and after modification to get evolutions of this profile. to do this we will use [https://www.eclipse.org/emf/compare/ EMF compare]
 +
* Code migration action for each type of evolution of the profile
  
 
=Bugs=
 
=Bugs=
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=525483 Bug 525483] - Profile changes management and model migration
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=525483 Bug 525483] - Profile changes management and model migration

Revision as of 12:20, 23 November 2017

Context

When a profile change we have to reapply it in all models whose apply it. This action of simply reapply this profile could lose some information and the model can become invalid.

Proposition

A new tool which will allow to migrate a profiled model when the profile evolve. This means that it will reapply the profile and ask the user some action to modify the model according to the modification of the profile. For example, if a stereotype becomes abstract then we will ask the designer if he wants to replace the abstract stereotype by a specification of this stereotype.

Actions to tackle

  • Compare profile before and after modification to get evolutions of this profile. to do this we will use EMF compare
  • Code migration action for each type of evolution of the profile

Bugs

  • Bug 525483 - Profile changes management and model migration

Back to the top