Turning a new leaf

Grails 3.0 built upon Spring Boot and Gradle

Natali Vlatko
Three image via Shutterstock

The embattled Grails framework has proudly produced Grails 3.0, a completely re-written project piggybacking on Spring Boot and Gradle. The release also marks the end of the line for Grails staff at software giant Pivotal.

Graeme Rocher, pioneer of the Grails framework, has announced the release of Grails 3.0. He has coincided the release with the team’s last working day at Pivotal, with several options available for the framework to consider in the coming months.

The latest release has been described as a “dramatic reimagining of the framework”, rewritten on the back of Spring Boot 1.2 and Gradle. Support for application profiles has also been included, which allows for application profiles with different pre-defined configurations and dependencies.

The core API has been rewritten around Groovy Traits, with the Grails API redesigned so that the public API is correctly populated under the grails. package. The private/internal API can be found in the org.grails. package.

SEE ALSO: Project lead Graeme Rocher on the future of Grails

With Gant now being replaced in version 3.0, the update features a new interactive command line shell that integrates closely with Gradle. The Gradle build also means that users can now import a Grails project using IntelliJ IDEA or GGTS’s Gradle tooling support, without the need for Grails specific tooling.

A complete list of all new features can be found on GitHub.

Destination unknown… for now

The future of the Grails project still lingers in unknown territory, with Rocher using the team’s last working day at Pivotal to reflect on the journey:

It has been a quite wonderful journey, from the exciting days of birthing a startup, to being acquired by SpringSource where I got to work with some of the most talented people in the industry. It is unfortunate that the company that exists today (Pivotal) is very different to what SpringSource was and is going in a new direction which Groovy and Grails have no part of. Nevertheless, I count myself as privileged to have had the chance help define the future of application development on the JVM during my time there.

Rocher says that Grails is still engaged in talks with several companies about continued sponsorship of the framework and “hope to have something to announce soon”.

While Groovy has officially joined the Apache Foundation, Rocher believes that Grails will eventually head down the foundation route too.

Natali Vlatko
An Australian who calls Berlin home, via a two year love affair with Singapore. Natali was an Editorial Assistant for (S&S Media Group).

Inline Feedbacks
View all comments