1

I am making an attempt to evaluate EMF for use within a project. One of the things i am looking at is some kind of versioning support at the metamodel (M2 or the .ecore model) level.

In terms of metamodel evolution, i have read certain discussions and have come across this paper. However, i wanted to know if there is anything concrete in this direction that is happening within EMF.

In general, what is the level of support for features involving versioning - such as merge and compare, evolution, migration, co-existence of multiple versions simultaneously, etc. I realize that the actual versioning itself will be provided by the source control system that one would use to store these meta-models, however semantic versioning capabilities (such as the ones i have mentioned above) should be provided by EMF itself, right?

I am aware of certain initiatives such as EMF Compare and Temporality which are meant for the EMF models. I am not sure if these work at the meta-model level.

4

2 に答える 2

2

私は博士論文でメタモデルの進化に取り組んでいます。私のアイデアの適用可能性を示すために、COPE と呼ばれる EMF でのメタモデルの進化をサポートするツールを開発しました。Web サイトでは、COPE に関する多数の出版物にアクセスしたり、ツール自体をダウンロードしたりできます。さらに、私は現在、COPE を EMF に貢献するプロジェクトを提案しています。

于 2009-04-23T05:09:43.973 に答える