EMF Model Migration: Edapt Graduation and 1.0 Release

EMF Model Migration: Edapt Graduation and 1.0 Release

Finally, we have graduated and released Edapt 1.0! Edapt has been in productive use in several projects for quite some time now, but was still not graduated. This has finally changed. Congrats to the team!

What is Edapt?

Edapt is an EMF framework to migrate instances of EMF models. Whenever you change your Ecore, all instances conforming to your old Ecore version might become invalid. If you have already released the software based on your Ecore model, you will need to migrate all instances of this model. This is typically a tedious and error-prone task. With Edapt you can highly automate this work.

How does Edapt work?

Edapt integrates into the Ecore Editor in your IDE and records all changes to the Ecore in a history. The history consists of the different releases and the changes that have been performed on the Ecore for a certain release. Based on the history, Edapt can migrate your model instances automatically at run-time. For this purpose Edapt provides a run-time component with an API to migrate model instances. This API is typically used in your application to detect and migrate out-of-date model instances before loading them into an editor or your UI.

How do I get started with Edapt?

1. Install the latest Edapt version from the p2 update site on our webpage.

2. Try the Getting-started Tutorial. More blog posts on Edapt will follow, stay tuned. We are looking forward to your feedback, check out the Edapt webpage!

 

 

Screenshot of EMF Ecore Editor with EdaptHistory

Screenshot of EMF Ecore Editor with EdaptHistory

2 Comments
  • Leonid
    Posted at 22:50, 2014-11-18

    Does EDapt has any plans of CDO integration? I’ve seen cdo support branch, but it doesnt’ seem to be working.

    • Posted at 10:16, 2014-11-19

      Hi, this was an experimental branch by one of our comitters to show feasibility. Are you interested in migrating CDO data with Edapt?