Last updated by 2 years ago

Page: STS FAQ, Version:25

This FAQ answers common questions about the Groovy and Grails support in the SpringSource Tool Suite (STS), and is up to date as of the 2.5.2 release of STS.

What is STS?

STS is an Eclipse-based IDE that provides a solid development environment for building Spring and Grails-powered enterprise applications.

How do I install the Groovy and Grails support?

In this release of STS, both the Groovy and Grails support must be installed through the extensions mechanism. To find the extensions, open the STS Dashboard then click the 'extensions' tab at the bottom of the dashboard window. For detailed instructions about how to do this (including screenshots), see: STS Integration. (You will need to be online for this the install to work.)

Why do I see 2 Grails icons on the extensions page and do I need to install both of them? What about Groovy support?

The first icon corresponds to the Grails runtime (the Grails package you would typically download from grails.org). The second corresponds to the Grails tool support inside of STS.

Groovy tool support is required because it is a prerequisite for Grails tool support.

A recent Grails runtime is required for the STS Grails tools to work. However, you do not need to install it from the extensions page if you already have one on your hard drive. In this case, you can instead manually configure your Grails runtime by going to Preferences -> Groovy -> Grails in your running STS.

What versions of Grails does STS support?

STS provides full support Grails versions 1.2.0+. Projects that use earlier versions of Grails can still be imported into the workspace, but they must be upgraded to use a more recent version of Grails.

Where do I start with Grails?

For a basic description of how to create a new project or import an existing project into STS, also see: STS Integration. This also covers how to use the pop-up Grails console to invoke Grails commands.

What does Groovy-Eclipse do for me?

Groovy-Eclipse is a complete IDE for managing Groovy and Grails projects. It includes the standard Eclipse IDE features like content assist, searching, navigation, refactoring, debugging, and version control as well as Groovy-Specific features like type inferencing and support for scripts. The full list of features can be found at Groovy-Eclipse's project home page

What does the Grails tool support do for me?

In addition to Groovy-Eclipse, STS's Grails tooling provides many useful features for developing Grails applications:
  • A plugin manager to browse and install Grails plugins
  • A command launcher
  • Content assist, navigation, and type inferencing for Grails specific DSLs including dynamic finders
  • An editor for GSPs
  • Intuitive ways to launch Grails commands
  • A Grails project view, specifically tailored towards Grails applications
  • Enhanced debugging of Groovy applications, so that Eclipse's Display view and Expressions view can evaluate Groovy expressions.
  • Ability to run Grails applications on tcServer, that provides enhanced diagnostics and allows you to analyze your Grails apps using Spring Insight.

How do I increase the memory used to run my Grails commands?

Define a Grails Run configuration and pass a high -XmxNN setting (e.g., 768 or 1024) in the JVM arguments section

Where do I raise a feature request or report an issue?

Groovy-Eclipse and Grails tool support are separate projects and use separate issue trackers.

Groovy related issues and features are handled on the codehaus Jira for the Groovy-Eclipse project, accessible here: http://jira.codehaus.org/browse/GRECLIPSE

For Grails-related issues, feature requests, and bugs, please use the STS Jira issuetracker.

Before raising an issue, you may want to send a message to the Groovy-Eclipse mailing list, or post to the STS forum.

What features are planned for the future?

You can browse open Grails issues on the STS jira. And open Groovy-Eclipse issues can be browsed as well.

You can also keep an eye on the SpringSource Tools Team Blog.

Where can I ask questions about the Groovy Eclipse support?

Feel free to ask at the STS forum or join the Groovy-Eclipse mailing list on Codehaus.

What is the best way to check my Grails project into a source code repository?

See Checking Projects into SVN

Help, I can't install Groovy-Eclipse!

Are you getting an error from p2 that looks something like this? (p2 is Eclipse's install and provisioning manager.)

Cannot complete the install because of a conflicting dependency.
 Software being installed: Groovy-Eclipse Feature
2.1.1.xx-20101124-2100-e36
(org.codehaus.groovy.eclipse.feature.feature.group
2.1.1.xx-20101124-2100-e36)
 Software currently installed: Shared profile 1.0.0.1284044844810
(SharedProfile_SDKProfile 1.0.0.1284044844810)
 Only one of the following can be installed at once:
   Java Development Tools Core 3.6.1.xx-20101124-2100-e36
(org.eclipse.jdt.core 3.6.1.xx-20101124-2100-e36)
   Java Development Tools Core 3.6.1.v_A68_R36x (org.eclipse.jdt.core
3.6.1.v_A68_R36x)
 Cannot satisfy dependency:
   From: Shared profile 1.0.0.1284044844810 (SharedProfile_SDKProfile
1.0.0.1284044844810)
   To: org.eclipse.jdt.core [3.6.1.v_A68_R36x]
 Cannot satisfy dependency:
   From: Shared profile 1.0.0.1284044844810 (SharedProfile_SDKProfile
1.0.0.1284044844810)
   To: org.eclipse.jdt.feature.group
[3.6.1.r361_v20100714-0800-7z8XFUSFLFlmgLc5z-Bvrt8-HVkH]
 Cannot satisfy dependency:
   From: Groovy-Eclipse Feature 2.1.1.xx-20101124-2100-e36
(org.codehaus.groovy.eclipse.feature.feature.group
2.1.1.xx-20101124-2100-e36)
   To: org.codehaus.groovy.jdt.patch.feature.group [2.1.1.xx-20101124-2100-e36]
 Cannot satisfy dependency:
   From Patch: org.codehaus.groovy.jdt.patch.feature.group
2.1.1.xx-20101124-2100-e36 Eclipse Java Development Tools
3.6.1.r361_v20100714-0800-7z8XFUSFLFlmgLc5z-Bvrt8-HVkH
(org.eclipse.jdt.feature.group
3.6.1.r361_v20100714-0800-7z8XFUSFLFlmgLc5z-Bvrt8-HVkH)
   To: org.eclipse.jdt.core [3.6.1.xx-20101124-2100-e36]

In particular, note the mention of SharedProfile_SDKProfile. This means that you are trying to install Groovy-Eclipse into a shared install of Eclipse (i.e., the directory is read-only). This is a known issue. See: Bug 332158 on Eclipse.org's bugzilla.

The solution is to make the STS directory writable and retry. We are working with the p2 team to fix this.

Help! I just installed Groovy-Eclipse and now I have lost all Java functionality.

It is likely that you are are coming across this problem GRECLIPSE-953. This may be an issue with a malformed download of the JDT core patch. The solution is:

  1. Uninstall Groovy-Eclipse.
  2. Download a zipped version of the update site, which you can find here for Groovy-Eclipse 2.1.1 and here for development builds).
  3. Point your Eclipse update manager to the downloaded zip file and install from there.
Again, this appears to be a p2 problem and may have something to do with being behind a proxy. We are working with the p2 team to get this fixed. See bug 334012

Drag-and-drop my Grails project onto Tc Server is not working

You should be able to drag-and-drop a Grails app onto a TcServer instance provided that you are using a recent version of STS (2.5.2 recommended) and TcServer (2.1 recommended). However there is a known bug that causes this not to work until you restart STS when you import a project into your workspace, from the file system and you do not select the "Copy files into workspace" option.

The issue is documented here: STS-1451.

The issue should be fixed in the latest nightly build. A workaround for 2.5.2 is to restart STS after importing a linked Grails project.

Where do I get help?

The best place to get help for any STS Grails problems is the SpringSource Tool Suite forum at http://forum.springsource.org/forumdisplay.php?f=32. The getting started guide for installing the Groovy and Grails support into eclipse is on this website: http://www.grails.org/STS+Integration#

Where do I report issues?

Issues with the Grails tooling should be reported on the STS issuetracker: https://issuetracker.springsource.com/browse/STS. Issues with the Groovy language support in STS should be reported on the Groovy-Eclipse issue tracker: http://jira.codehaus.org/browse/GRECLIPSE. If unsure, just raise an STS issue and we'll do the rest.