Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341852

Summary:	Encode custom migrations in Java
Product:	[Modeling] Edapt	Reporter:	Markus Herrmannsdoerfer <herrmama>
Component:	Core	Assignee:	Markus Herrmannsdoerfer <herrmama>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Markus Herrmannsdoerfer

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

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.