Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341784

Summary: Switch from migrator generation to interpretation of the history
Product: [Modeling] Edapt Reporter: Markus Herrmannsdoerfer <herrmama>
Component: CoreAssignee: Markus Herrmannsdoerfer <herrmama>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Markus Herrmannsdoerfer CLA 2011-04-04 09:58:05 EDT
Currently, a migrator plugin is generated from the history that can be used to migrate model instances. However, the history of Ecore models could also be directly interpreted to migrate model instances. When interpreting the history model, the step to generate the migrator is no longer necessary, simplifying the process of using Edapt.
Comment 1 Markus Herrmannsdoerfer CLA 2011-05-13 13:14:55 EDT
Now, the history is interpreted directly to migrate models. Instead of registering the directory with the generated migrator, the history is directly registered through an extension point. As a consequence, we can also provide a means to execute a migration as a launch configuration. The launch configuration allows the users to set the parameters of a migration, i.e. the model to be migrated, the source release, and so on.