eclipse-ecp-bot
commented
6 months ago Jul 15, 2020 13:13
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.
If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
--\ The automated Eclipse Genie.
| --- | --- | | Bugzilla Link | 535685 | | Status | NEW | | Importance | P3 normal | | Reported | Jun 08, 2018 06:36 EDT | | Modified | Jul 06, 2022 05:40 EDT | | Reporter | Lucas Koehler |
Description
This is a follow up bug of the string-based template model migration introduced in Bug 533299
The template model and view model migration should be refactored to use common functionality from common migration bundles.
Currently, the view model and the template model migration are completely separated from each other. Additionally, the template model migration is only based on string substitution. Furthermore, classes like TemplateModelMigrationUtil or TemlateModelWorkspaceMigrator are part of the view.migrator bundle.
-> The migration should be refactored to have a common Edapt-based migrator and (if necessary) subclasses with specific details for view and template models. The basic Edapt migrator should be located in a common migration bundle. For this, most functionality should also be present in the EdaptViewModelMigrator.
Currently, the logic for checking for migrating files in the workspace is duplicated between the view and the template editor (except for\ searching for model files, this is in WorkspaceUtil in the ide.util bundle).
-> The workspace migration should be centralized in a common workspace migration bundle and check for all "EMF Forms" models (currently view\ and template). This includes the dialogs prompted to the user as well as executing the migration.