First8 staat voor vakmanschap. Al onze collega’s zijn een groot aanhanger van Open Source en in het bijzonder het Java-platform. Wij zijn gespecialiseerd in het pragmatisch ontwikkelen van bedrijfskritische Java toepassingen waarbij integratie van systemen, hoge eisen aan beveiliging en veel transacties een belangrijke rol spelen. Op deze pagina vind je onze blogs.

Eclipse Neon: Grails 2.x with Groovy and GSP Support

What if you want to develop Grails 2 projects with Eclipse Neon (4.6) as easy as you did with Groovy/Grails Tool Suite? Written and tested with Eclipse Neon and Grails 2.3, 2.4 and 2.5.


Disclaimer: this post is a complete copy of my awesome colleague Ted Vinke’s post about eclipse Mars of last year!

Actually, this is of course only partly true. This post is targeted towards Grails 2 and provides pointers on how to create a minimal install of Eclipse, which is great since code is a liability: more code means more bugs!

The Eclipse landscape for Grails development is a bit shady. Yes, the Getting Set Up in an IDE documentation of the currently latest version refers to Groovy/Grails Tool Suite as the recommended IDE for Eclipse users. However the latest GGTS to be downloaded from is which is based on Eclipse Luna SR1 (4.4.2) — not Eclipse Neon.

The Grails IDE plugin — which is the core component for grails 2 — hasn’t been updated since Grails 3 came along and Pivotal dropped support. Luckily for us, it still ‘Just Works!’.

Although Eclipse is not perfect, it is a really powerful tool if you know how to change it to your needs. It is flexible enough to support many languages, tools and workflows. This flexibility comes at a price, in the shape of many plugins that have interdependencies. All these dependencies create many opportunities to have bugs that cause failure. You don’t want that. Use fewer plugins.

A minimal install

In order to have as little bugs as possible, you may want to eliminate all plugins that you don’t need. Here’s one way to get there.

  • Make sure that a Java 8 (from oracle for instance) jdk (not jre) is the default version of Java for your machine
  • Download the Java package of eclipse:
  • Extract to your favorite location
  • Start Eclipse
  • Go to Help → Installation details
  • Uninstall the following items (unless you actually enjoy using mylyn, or also use maven?):

    Code Recommenders Mylyn Integration
    Eclipse Git Team Provider - Task focused interface
    m2e - slf4j over logback logging (Optional)
    Mylyn Builds Connector: Hudson/Jenkins
    Mylyn Context Connector: Eclipse IDE
    Mylyn Context Connector: Java Development
    Mylyn Task List
    Mylyn Task-Focused Interface
    Mylyn Tasks Connector: Bugzilla
    Mylyn Versions Connector: Git
    Mylyn WikiText
  • Confirm restarting Eclipse


Installing what you need

Adding stuff is easy using the marketplace, but could go a lot quicker (if you know what you need).

The result is a lightweight version of Eclipse completely usable and perfect for maintaining those Grails 2 applications that you might have.


Start with an Oomph

When the minimal install we just created here is not exactly what you need or you want to create some other specific version of eclipse, try using Oomph.

Oomph is an easy way to create an eclipse for each purpose because creating a new installation is very quick! You can, for instance, start with just the basic eclipse without any programming language support and start installing plugins from there.


Work fast, code happily

Happy coders make creative and productive coders! There is a lot more to tell about eclipse and the elaborate landscape of plugins that it provides for working with, for example Javascript, Regexes, your own DSL’s, etc, etc. so stay tuned for more posts!

Braam Wijsmuller