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

Bug 343478

Summary:	Get rid of dependency on Groovy
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-21 02:42:28 EDT

Currently, Edapt depends on an older version of Groovy. However, we want to get rid of the dependency on Groovy for the following reasons:

- Groovy was changed in a non-downwards-compatible manner. Therefore, it would required considerable effort to migrate to the new version of Groovy.

- A lot of potential Edapt users stated that they do not want to learn a new language to implement migrations. Rather they want to use Java, the language that they are already familiar with.

- Since Groovy is a dynamically typed language, it does not provide as good code completion as statically typed languages which makes it difficult to implement migrations.

- A dependency on Groovy requires approval by the IP team. To be able to use Edapt without this approval, we want to get rid of the Groovy dependency.

Comment 1 Markus Herrmannsdoerfer

2011-05-13 13:25:56 EDT

Since both reusable and custom migrations can be specified in Java, we can get rid of the dependency on Groovy.