Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341852 - Encode custom migrations in Java
Summary: Encode custom migrations in Java
Status: RESOLVED FIXED
Alias: None
Product: Edapt
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Markus Herrmannsdoerfer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 18:22 EDT by Markus Herrmannsdoerfer CLA
Modified: 2011-05-13 13:19 EDT (History)
0 users

See Also:

Attachments
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 Markus Herrmannsdoerfer CLA 2011-04-04 18:22:37 EDT 
Currently, custom migrations need to be encoded in Groovy. Since Groovy is a new language that has to be learned by developers, it would be better to specify custom migrations in Java. Thereby, Groovy should be replaced by Java.
Comment 1 Markus Herrmannsdoerfer CLA 2011-05-13 13:19:02 EDT 
Custom migrations can now be specified in Java classes. These classes have to inherit from the class CustomMigration which provides methods to perform the migration before or after the metamodel adaptation. Thus, in contrast to Groovy, the specification of the metamodel adaptation is no longer part of the specification of the custom migration. Moreover, the custom migration specification is no longer stored inside the history model, like was done for Groovy migrations. There is also support to create and edit a custom migration.