Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343478 - Get rid of dependency on Groovy
Summary: Get rid of dependency on Groovy
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-21 02:42 EDT by Markus Herrmannsdoerfer CLA
Modified: 2011-05-13 13:25 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-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 CLA 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.