Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current ·  View Page History
<< Previous Version 124 Next >>

This page has information about GroovyEclipse Plugin v2. For information about v1 of the plugin, see About GroovyEclipse Plugin v1.

Features and Status

The GroovyEclipse Plugin provides Eclipse-based tooling support for the Groovy programming language. GroovyEclipse allows you to edit, compile, run, and debug Groovy scripts and classes from the Eclipse SDK.

Key Features

  • Syntax highlighting
  • Compile and run Groovy classes and scripts in Eclipse
  • Outline view for Groovy files
  • Auto-completion
  • Refactoring
  • Source code formatting

Read about the goals, approach, and implementation of GroovyEclipse v2 at http://blog.springsource.com/2009/07/30/a-groovier-eclipse-experience/.

See what's new in the M1 release at Groovy-Eclipse 2.0.0M1 New and Noteworthy.

Eclipse Version Compatibility

GroovyEclipse Plugin v2 supports 3.4.2 and 3.5.n

Availability

Milestone 1 build is released. General availability is planned for year-end 2009.

Getting Builds

Milestone and development builds are available. A milestone build is a relatively stable build, released at the completion of a project milestone. Development builds are are published more frequently, and contain more new features and fixes. Published development build have passed unit tests, but may be less stable than milestone builds.

Milestone Builds

GroovyEclipse v2.0 Milestone 1 (M1) is available for Eclipse 3.5 at: http://dist.springsource.org/milestone/GRECLIPSE/e3.5/

Development Builds

Development builds for Eclipse 3.5 are at:
http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.5/

Development builds for Eclipse 3.4 are at:
http://ci.repository.codehaus.org/greclipse/snapshot/e34/

Archived Development Builds

Archived snapshots of the plugin are available at:

http://ci.repository.codehaus.org/greclipse/snapshot/e35/old/

These zip files are the compressed version of the update site. They are not plugins that you can just drop into your eclipse installation. Here's how to install an archive:

  1. Download the snapshot locally
  2. Do not unzip or move into your dropins directory
  3. Start eclipse
  4. Help -> Install new software -> Add...
  5. Select the location of the zip you just downloaded
  6. Install as you would from the regular update site

Important: GroovyEclipse plugin will only install on Eclipse 3.4.2 or Eclipse 3.5 or 3.5.1 because a specific version of the JDT feature is required. See Groovy Eclipse FAQ for more information.

Getting Started with GroovyEclipse v2

This section has brief instructions for getting started with GroovyEclipse 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.

FAST FACTS: 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 GroovyEclipse Plugin tutorial.

FAST FACTS: How to Create a Groovy Project

To create a basic Groovy project in Eclipse perform the following steps:

  • Open the Java perspective
  • Click on the new Groovy Project icon:
  • The new project wizard for Groovy uses most of the same options as the new project wizard for Java.
  • Fill in the appropriate details and create the project.

You should have a src folder and several libraries. A bin folder is also created, but is hidden.

You can create a Groovy classes or test cases using wizards similar to the Eclipse's Java class and JUnit test case wizards. Use the options on the File > New menu or press CTRL-N.

For step-by-step instructions, see the Create Your First Groovy Project tutorial.

FAST FACTS: How to Test the Plugin

It is a good idea to test the plugin before installing in your regular Eclipse installation. The main test project is org.codehaus.groovy.alltests. To run the tests, right-click on the project and select Run As->JUnit Plug-in Test.

Information Resources

Use the resources listed below to learn about GroovyEclipse Plugin v2 and keep abreast of project status and milestones.

FAQs

See Eclipse Plugin V2 FAQ.

Tutorials

The first two of a series of tutorials on using GroovyEclipse Plugins v2 are available.

Mailing Lists

Join GroovyEclipse mailing lists to find answers, ask questions, and contribute to discussions about v2 of the plugin.

Developer Resources

Source Code

The GroovyEclipse Plugin v2 SVN repository is at http://svn.codehaus.org/groovy/eclipse/trunk/. If you are new to Subversion, see Subversion home page.

If you wish to view but not download the source code, use FishEye.

If you wish to download sources, use of Subversive to check out the source code.

The plugin source contains Groovy source files. You must have a groovy compiler to build the plugin. Groovy compilers are included in the plugin distribution, which you can download from from http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.5/ or http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.4/.

Building and Installing an Update Site

Building the Update Site

Instructions tbs. If you plan to build an update site, please contact{{http://xircles.codehaus.org/lists/eclipse-plugin-dev@groovy.codehaus.org}}.

Installing the Update Site

An update site you create can be installed with the Eclipse update manager. Install the Groovy feature, using the instructions in the How To Install section above, but use a "Local Site" that points to the GroovySite directory you created, instead of a "Remote Site".

Open Issues

jiraissues

Labels
  • None