Groovy-Eclipse is the set of Eclipse plugins that provide Eclipse support for Groovy projects.
The latest Groovy-Eclipse release is available from the following Eclipse update sites. To install, point your Eclipse update manager to the update site appropriate for your Eclipse version or drag and drop the marketplace icon into your Eclipse installation.
|Eclipse level||Release update site|
|4.4 (Luna)||snapshots available (see below), release imminent|
|4.2 and 3.8 (Juno)|
Or, you can choose to install a development build, see below for more update sites. In general, our development builds are quite stable. A development build is not published unless all unit tests pass.
This service refresh of Groovy-Eclipse provides significant improvements with the
The install directory must be writable by the current user. Groovy-Eclipse cannot be installed into a shared install. This includes protected directories on windows like
This service refresh of Groovy-Eclipse provides some bug fixes as well as notification of compiler level mismatches between the workspace and individual projects. See all the details: Groovy-Eclipse 2.7.1 New and Noteworthy. (September 23, 2012)
The Groovy-Eclipse build server has moved. The new location is at https://build.springsource.org/browse/GRECLIPSE. The old location at http://bamboo.ci.codehaus.org/browse/GRECLIPSE will be available for historical reasons. (August 3, 2012)
The Groovy-Eclipse team is proud to announce the 2.8.0 release. This release includes significant memory and performance improvements, as well as Editor templates and almost 100 bugs fixed. See read more at the Groovy-Eclipse 2.8.0 New and Noteworthy. (July 39, 20122013)
|Table of Contents|
Groovy-Eclipse allows you to edit, compile, run, and debug Groovy scripts and classes from the Eclipse SDK.
- Syntax highlighting
- Type inferencing
- Compile and run Groovy classes and scripts in Eclipse
- Outline view for Groovy files
- Source code formatting
- Basic debug support
- Groovy 2.1, 2.0, 1.8 and 1.7 compilers
- DSL support using DSL descriptors
- Maven integraion
Read about the goals, approach, and implementation of Groovy-Eclipse v2 Eclipse here.
New and Noteworthy
For information about prior releases, see here:
- Groovy-Eclipse 2.7.1 2 New and Noteworthy
- Groovy-Eclipse 2.7.0 New and NoteworthyGroovy-Eclipse 2.6.1 New and Noteworthy
- Groovy-Eclipse 2.67.0 New and Noteworthy
- Groovy-Eclipse 2.5.2 New and NoteworthyGroovy-Eclipse 18.104.22.168 New and Noteworthy
- Groovy-Eclipse 2.56.0 New and NoteworthyGroovy-
Eclipse Version Compatibility
Groovy-Eclipse Plugin v2 supports Eclipse versions 4.4.x, 4.3.x, 4.2.x, 3.7.x, 3.6.x, 3.5.x, and 3.4.2. Groovy-Eclipse for Eclipse 3.6 and earlier are no longer supported, but the builds are still available.
By default, Groovy-Eclipse comes with a 12.8 0 and 1.7 8 Groovy compiler. A Groovy 2.0 1 compiler can optionally be installed from the Groovy update site. See Compiler Switching within Groovy-Eclipse for more information.
We occasionally release milestone builds of upcoming releases. These are meant for users who want to have access to the most recent features and who are willing to give us feedback on them.Groovy-Eclipse milestone and release candidate builds are available at:
|Eclipse level||Milestone update site|
|4.2 / 3.8 (Juno)|
Please note that these builds are temporary and are typically removed after the final release has been made public.
Development Snapshot Builds
Use one of these update sites to install the latest and greatest Groovy-Eclipse. Development builds tend to be quite stable (they are not released unless all tests pass) and so if you are having any difficulty with your current install, then it is recommended to update to the latest dev build. To install, paste the appropriate update site below into your Eclipse update manager, select the artifacts to install and follow the instructions.
|Eclipse level||Development update site|
|4.2 / 3.8 (Juno)|
Although these builds may not be as stable as milestone or release builds, they pass our suite of unit and integration tests. These builds are typically usable, and if there is a problem it is often fixed quickly.
Archived Development Builds
|Eclipse level||Development update site zip|
|4.2 / 3.8 (Juno)|
Getting Started with Groovy-Eclipse v2
This section has brief instructions for getting started with Groovy-Eclipse v2. The instructions assume familiarity with Eclipse. Users new to Eclipse, may wish to follow the links to tutorials, which illustrate and provide novice level instructions for installing and using the plugin.
How to Install
- Go to: Help -> Software Updates.
- Change to the Available Software tab.
- Click on Add Site.
- Paste the update site URL appropriate for your version of Eclipse and click OK.
- You should see a "Groovy Update Site" entry in the list of update sites. Expand and select the Groovy-Eclipse Plugin feature. Optionally, you can choose to include the sources..
- Click Install and follow the prompts.
- Restart when asked
- Rejoice! You installed the Groovy-Eclipse Plugin v2.
For step-by-step installation instructions, see the Install Groovy-Eclipse Plugin tutorial.
Use the resources listed below to learn about Groovy-Eclipse Plugin v2 and keep track of project status and milestones.
- The CI Server for Groovy-Eclipse is located at the Bamboo server. (Note that this is a new location as of August 3, 2012.)
- The Groovy-Eclipse Plugin v2 git repository is located at https://github.com/groovy/groovy-eclipse. If you are new to github and git, you can familiarize yourself by reading some good tutorials at github.
- The Groovy-Eclipse Plugin v2 SVN repository is now deprecated. For historical reasons, you can still access it at at
http://svn.codehaus.org/groovy/eclipse/trunk/. If you are new to Subversion, see Subversion home page.The plugin source itself is partially written in Groovy. And for that reason, you must have Groovy-Eclipse installed before you can compile Groovy-Eclipse.
- If you are interested in working Groovy source code or plan to do a local build, please contact the eclipse plugin dev mailing list and we can help you out.
- See a list of bugs suitable for community members to work on. All the issues labelled help requested are a good place to start.