The latest expert opinions, articles, and guides for the Java professional.

JRebel 6.1 – Grails and WildFly!

Everyone on the JRebel team at ZeroTurnaround is proud to announce the newest release of JRebel. We’ve got something really exciting to announce, Grails is now supported!


One of the questions that kept popping up over the years is, “do you support Grails?” and until now things kind of worked, but not great. As of today, with the release of JRebel 6.1, Grails is officially and fully supported with JRebel. Developers using Grails can expect the same quality integration as with our other fully-supported frameworks like Spring.

Hot code reloading is not new to Grails developers, spring-loaded is included in the Grails distribution. However, let’s face it, if spring-loaded provided everything that is needed, we wouldn’t be getting so much demand for Grails integration. Spring-loaded only supports a few use cases and is inconsistent in its reloading capabilities. Many Grails devs disable spring-loaded because it just isn’t worth it. Developers disable spring-loaded with the “-noreloading” argument because the inconsistency makes debugging significantly trickier and sometimes completely offsets any productivity gains.

”Grails comes with its own reloading, but that has proven to be just flakey enough where I don’t trust it. Using JRebel, I find the opposite: the application reloads reliably and predictably. That means I can focus on the product, not the tools.”

Now, Grails developers have a good, stress-free answer to their reloading problem. With full Grails support, JRebel provides a consistent experience with support for reloading all Java, Groovy, and other JVM code changes. Not to mention the support for over 90 other frameworks at the time of this launch. :)

With JRebel, while writing Grails applications, you’ll be able to scaffold and modify code and see it reloaded into the JVM without having to go through a full build or restarting your application and be well on your way to saving over one full work month each year.

This release will also make WildFly users happy. JRebel 6.1 contains a ton of improvements to the Java EE support for WildFly. We have gone through all of the unsupported use cases reported by JRebel users and have “made the tests green” so to say. Our CI for WildFly looks like the proverbial “green field” and you will notice a much more seamless experience developing Java EE applications on WildFly with JRebel.

There are other improvements and upgrades as well. The NetBeans plugin has a more streamlined install and configuration experience, and the IntelliJ plugin has upgraded logging support. We have also enhanced our support for Spring Data REST. As well as a few new integrations for application servers:

  • Tomcat 8.0.17
  • Jetty 9.2.7
  • Liferay 6.2.2 GA3

For existing JRebel users, get the latest release by upgrading your IDE plugin or heading to the download page.

For new users, try JRebel for free for 14 days and see how much time you’ll save!

Responses (6)

  1. Avatar  


    February 27, 2015 @ 10:25 am

    Hi, cool video. But how must i configure jrebel with grails. My problem is that i must manually call ‘grails compile’ to start the compile process. How does it work in the video?

  2. Avatar  

    Adam Koblentz

    March 2, 2015 @ 12:30 am

    Hi Alex, you can configure JRebel with grails by adding the jrebel jar as a javaagent to your GRAILS_OPTS or your JAVA_OPTS. If you’re using an IDE, make sure build automatically is enabled. If you’re not using any IDE, you need to either call grails compile or use the grails interactive mode so it compiles classes as they’re changed. Thanks!

  3. Avatar  

    YanLu Liu

    March 9, 2015 @ 5:29 pm

    Hi, I have a grails 2.3 application with spring annotation beans in java.
    In grails buildConfig.groovy file there is
    // packages to include in Spring bean scanning
    grails.spring.bean.packages = [“”]

    When the grails 2.3 app is started with JRebel agent enabled, the controllers and services in groovy files are reloaded by JRebel-Grails. But while I write a spring bean class in java as following, the JRebel-Spring plugin is not working.

    public class CfgSampleAServiceImpl implements CfgSampleAService {

    public String doGetSampleAInfo() {
    return “Sample-A”;


    My question is “As Rebel-Grails2 plugin is active, is the Rebel-Spring plugin disabled as default?”

  4. Avatar  

    Adam Koblentz

    March 9, 2015 @ 5:45 pm

    Hi YanLu,

    The spring plugin should also work, as spring is integral to grails. Please send an email to our support team – and they’ll be able to assist you.

  5. Avatar  

    Brian Saville

    March 18, 2015 @ 5:53 pm

    As a friendly note, calling it “Groovy on Grails” is a good way to turn off experienced Grails developers to looking at it. See this SO post for a little more background:

  6. Avatar  

    Twinkle Thakkar

    December 29, 2015 @ 1:16 pm

    Does this support changes made in config files – config.groovy / datasource.groovy?

RSS feed for comments on this post.

Leave a comment