[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [henshin-dev] Should we introduce a new model version after renaming and restructuring model elements?
|
Hi Felix,
you can try out the transformation models in the tests plug-in. They all
load just fine (e.g. in the editor or when running the tests).
Cheers,
Christian
On 09/20/2012 12:53 PM, Christian Krause wrote:
Hi Felix,
as I already wrote you in previous mail, I changed the model in such a
way that the old models can still be loaded transparently, that means
without any need for migration. I want to keep it that way. Thus, I
don't want to introduce a new version number.
It should be fairly simple to fix the existing migration code. Please
let me know if I shall fix the code.
Cheers,
Christian
On 09/20/2012 12:48 PM, Riegerf@xxxxxxxxxxxxxxxxxxxxxxx wrote:
Hi everyone,
recently, we decided to change the names of some classes and methods,
as well as to clean up the containment structure in order to improve
software quality, ease of use and understanding. This led, however,
to a change in the model. Since both the original and the refactored
2011 model are very similar, it didn't appear neccessary to issue a
new model version. As it turns out, some of our code seems to have
problems with the new model. Since we do not know how our users use
Henshin in their projects, I propose to issue a new "2012" model
version instead of changing the 2011 model without changing its
version. Doing so will lead to less confusion. Migration should be
pretty straightforward and will only consist in renaming elements.
What do you think?
Felix
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
