Community
Participate
Working Groups
With 1.17.0 we change the NS-URI of the core view model. This will make DMR-Selectors invalid, so we also need a migration for template models. As a remark: The EdaptViewModel migrator also has API to migrate a string
New Gerrit change created: https://git.eclipse.org/r/121661
For a proper migration, the following steps would be necessary: - Create an EdaptTemplateModelMigrator similar to the EdaptViewModelMigrator - Therefore, extract common functionality from the EdaptViewModelMigrator to a common class - Integrate check in the TemplateModelEditorPart that checks whether a migration is necessary, and if yes prompts the user about this (see ViewEditorPart) - Add test cases: RCPTT and/or plugin test Estimated development time: 5 days (3-6 days)
Addition: For o histories should be needed for the template model elements. Instead they can be generated on the fly (functionality is present in the EdaptViewModelMigrator)
*For now, no histories should be needed for the template model elements.
New Gerrit change created: https://git.eclipse.org/r/124244
Gerrit change https://git.eclipse.org/r/124244 was merged to [release_1.17.0]. Commit: http://git.eclipse.org/c/emfclient/org.eclipse.emf.ecp.core.git/commit/?id=a85b92021332e7ffa24aeba6a15214fbae2b5cbf
REGRESSION INFORMATION: If the user accepts migrating the opened view model, the view model editor additionally asks the user if (s)he wants to migrate template models in the workspace. If a template model needs migration, the template model editor prompts the user whether it should be migrated. If the user accepts, the editor additionally prompts whether template models in the workspace should be migrated. Follow up task for refactoring the migration of view- and template models: Bug 535685
