Bug 542673

Summary: [Segments] Provide migration with persistence from legacy DMRs to segments
Product: [Modeling] ECP Reporter: Lucas Koehler <lkoehler>
Component: EMF FormsAssignee: Lucas Koehler <lkoehler>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 Keywords: noteworthy, ui
Version: unspecified   
Target Milestone: 1.22.0   
Hardware: PC   
OS: Linux   
See Also: https://git.eclipse.org/r/142862
https://git.eclipse.org/c/emfclient/org.eclipse.emf.ecp.core.git/commit/?id=1c76384cba45f9de6b380d6513ba26ea773b4cda
https://git.eclipse.org/r/144086
https://git.eclipse.org/c/emfclient/org.eclipse.emf.ecp.core.git/commit/?id=42062e3c718692367676f6b20e5ad1c1079e38a8
Whiteboard:

Description Lucas Koehler CLA 2018-12-11 10:08:40 EST

    
Comment 1 Lucas Koehler CLA 2019-05-21 10:06:51 EDT
If the view tooling runs in segment mode, the ViewEditorPart should check on opening a viewmodel whether the view model still contains legacy domain model references. If yes, the user is queried whether (s)he wants to migrate the view model to segments. This happens after potential Edapt migrations.

The migration transforms all legacy DMRs to plain VDomainModelReferences and transforms the DMRs (including nested DMRs) to a segment path. Thereby, the legacy DMRs are replaced by the new DMR.
Comment 2 Eclipse Genie CLA 2019-05-27 10:00:28 EDT
New Gerrit change created: https://git.eclipse.org/r/142862
Comment 4 Eclipse Genie CLA 2019-06-14 14:31:09 EDT
New Gerrit change created: https://git.eclipse.org/r/144086
Comment 6 Lucas Koehler CLA 2019-06-17 04:32:16 EDT
Behavior was implemented as described in Comment 1.
Note: The migration is never offered to migrate legacy dmrs if the view model requires an edapt migration and the edapt migration is declined by the user.