|Re: [EMFStore][Edapt] Meta Model evolution [message #1780484 is a reply to message #1780260]
||Tue, 23 January 2018 08:22
| Johannes Faltermeier
Registered: December 2013
this was introduced with EMFStore 1.8 and requires Edapt 1.2 or higher.
In order to trigger a migration on server side, there is a special VM argument. Add the emfstore.migration=true VM argument to your server launch configuration. With this option the server will start in a migration mode, meaning that it will check if a migration is required, perform the migration, and stopping itself right after the migration was performed. Then you may start it regularly again.
Enabling the full project state persistence when a version is tagged, can be done via an extension point on server side:
For client side migration we suggest a process which notifiers users to commit pending changes, then migrate the server and roll out clients with the new model, where users will start with fresh checkout.
Get professional Eclipse developer support:
[Updated on: Tue, 23 January 2018 08:23]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03706 seconds