| Require thoughts on upgrading an EMF model [message #1016330] |
Wed, 06 March 2013 00:10  |
Eclipse User |
|
|
|
Hello all,
I am seeking some suggestions on the approach for upgrading a released EMF model. Here is the scenario:
I am part of a team that is expected to publish a base domain model as an Ecore model as an Ecore file and this would be consumed by other teams who can choose to embellish it as per their specific requirements.
The base domain model would however also keep changing as I get new requirements. How do I ensure that when the other teams take my new version, they will have minimal work and problems in merging my new version with their changes on the older version? Any suggestions?
Thanks.
|
|
|
| Re: Require thoughts on upgrading an EMF model [message #1016610 is a reply to message #1016330] |
Thu, 07 March 2013 01:59  |
| Eclipse User |
|
|
|
Sathya,
Comments below.
On 07/03/2013 1:34 AM, Sathya Sekar wrote:
> Hello all,
>
> I am seeking some suggestions on the approach for upgrading a released
> EMF model. Here is the scenario:
>
> I am part of a team that is expected to publish a base domain model as
> an Ecore model as an Ecore file and this would be consumed by other
> teams who can choose to embellish it as per their specific requirements.
>
> The base domain model would however also keep changing as I get new
> requirements. How do I ensure that when the other teams take my new
> version, they will have minimal work and problems in merging my new
> version with their changes on the older version? Any suggestions?
In general you should strive to produce source compatible APIs. So
don't rename or remove things (deprecate them if necessary) and only add
new things (classes, data types, features, operations). It's always
harder to manage the case of clients extending the model; they'll often
need to regenerate their model, or at least recompile it.
>
> Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.25389 seconds
Home