search

eclipse-ecp / org.eclipse.emf.ecp.core

Eclipse Public License 2.0
0 stars 0 forks source link

Auto Migration of EAnnotation.view (and potentially other view models) fails #50

Open eclipse-ecp-bot opened 7 months ago

eclipse-ecp-bot commented 7 months ago

| --- | --- | | Bugzilla Link | 511832 | | Status | NEW | | Importance | P3 normal | | Reported | Feb 07, 2017 07:34 EDT | | Modified | Jan 10, 2023 04:00 EDT | | Blocks | 462873 | | Reporter | Lucas Koehler |

Description

The automatic migration of EAnnotation fails with a ClassCastException. This is due to Edapt having problems with migrating models that have an EClass defined in Ecore as their rootEClass.\ Therefore, all viewmodels and simple viewmodels for the ecore editor should be migrated manually.

eclipse-ecp-bot commented 7 months ago

Jan 29, 2019 02:18

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.

eclipse-ecp-bot commented 7 months ago

Jan 19, 2021 03:05

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.

eclipse-ecp-bot commented 7 months ago

Jan 10, 2023 04:00

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.