Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362469 - Handle migration of recorded feature removal
Summary: Handle migration of recorded feature removal
Status: CLOSED WONTFIX
Alias: None
Product: Edapt
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-31 07:22 EDT by Lasse Bjermeland CLA
Modified: 2015-02-05 09:21 EST (History)
1 user (show)

See Also:

Attachments
Screen shot of unnecessary attribute migration (5.75 KB, image/png)
2011-10-31 07:22 EDT, Lasse Bjermeland CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lasse Bjermeland CLA 2011-10-31 07:22:24 EDT 
Created attachment 206202 [details]
Screen shot of unnecessary attribute migration

Migration of deleted attributes fails when the deletion is part of a recorded change. When the change is converted to a "Delete Feature" operation the migration   works as intended
Comment 1 Maximilian Koegel CLA 2015-02-05 09:21:32 EST 
This is intended behavior since just deleting the attribute from the metamodel does not say what to do with the data in instances. Using the DeleteFeature Operation explicitly states that. A use case where just deleting it from the meta model makes sense is a custom migration.