A few days ago Grails 3.0 was officially released. Grails is now based on Spring Boot, the build system changed from Gant to Gradle and significant parts of the framework have been rewritten. In this post we will have a look at all the major changes introduced by Grails 3.
Updated file structure
We will start with a screenshot that shows a fresh Grails 3 project created from the Grails command line using
grails create-app hello
The first two folders (build and gradle) are related to Gradle, the new build system in Grails 3. As the name implies, build is the directory where build related files like compiled classes and assembled packages are located. The gradle directory contains the Gradle Wrapper that allows you to build the project without a local Gradle installation.
The content of the conf folder has also been changed. The default format for configuration files is now YAML. If you prefer to write your configuration in Groovy, you can still create a grails-app/conf/application.groovy configuration file manually.
Logback is now the default logging provider. The logging configuration (previously part of Config.groovy) has been moved to conf/logback.groovy. Note that the conf folder is not a source directory anymore.
init is a new folder in Grails 3. It contains Bootstrap.groovy (same content as in previous Grails versions) and the new Application main class (we will look into this in the Spring Boot section).
The structure of the src folder has been changed to match Gradle conventions. Additional Java and Groovy files are now located in:
src/main/java src/main/groovy src/test/java src/test/groovy
build.gradle and gradle.properties contain the build configuration. BuildConfig.groovy from previous Grails versions does no longer exist.
Spring 4.1 and Spring Boot
Spring Boot is the new basis for Grails. According to Graeme Rocher Grails 3 is nothing less than a ground up rewrite on top of Spring Boot.
Like Spring Boot applications Grails 3 projects come with an Application class that has a standard main() method. This means you can start a Grails 3 application simply by running the main class from your IDE.
The default Application class looks like this:
class Application extends GrailsAutoConfiguration {
static void main(String[] args) {
GrailsApp.run(Application)
}
}Note that the war file you get when packaging the application can now be executed using the java -jar command:
java -jar build/libs/myApplication-0.1.war
This runs the main method which starts the application using an embedded Tomcat server. Of course you can still deploy the war file on an application server of your choice like in previous Grails versions.
The Application class acts as Spring configuration class. So, we can use Spring’s @Bean annotation to define custom beans. Methods like onStartup() or onShutdown() can be overwritten if you want to execute custom code at certain application events.
class Application extends GrailsAutoConfiguration {
...
@Bean
MyBean myBeanId() {
return new MyBeanImpl();
}
@Override
void onStartup(Map<String, Object> event) {
super.onStartup(event)
// custom startup code..
}
}Traits
In Grails components like Controllers or Domain classes always had some magically attached functionality. For example, in Controllers you can use methods like render(), redirect() or getParams() without subclassing another class. In Grails 3 these features have been rewritten to make use of T raits introduced by Groovy 2.3.
Certain Traits are automatically attached to Controllers, Services, Tag libraries and so on to make framework methods available. For example, a Controller automatically gets the following Traits: TagLibraryInvoker, AsyncController, RestResponder, Controller.
The cool thing with Traits is that you can easily add them to your own classes.
For example: Assume you want to access the request and params objects outside a Grails Controller. All you have to do now is adding the WebAttributes trait to your class:
class MyCustomComponent implements WebAttributes {
public MyCustomComponent() {
// make use of WebAttributes methods like getWebRequest() or getParams()
println "base url: " + webRequest.baseUrl
println "params: " + params
...
}
}Interceptors
Grails 3 introduced standalone Interceptors. Interceptors can intercept incoming requests to perform common tasks (e.g. logging, authentication, etc.).
A new Interceptor can be created using create-interceptor command:
grails create-interceptor MyInterceptor
A newly created Interceptor looks like this:
class MyInterceptor {
boolean before() {
// executed before a request is processed by a controller
true
}
boolean after() {
// executed after a request is processed by a controller
true
}
void afterView() {
// executed after the view has been rendered
}
}Interceptors replace Filters used by previous Grails versions. Filters still work in Grails 3 for backwards compatibility. However, they are considered deprecated now.
If you are aware of Spring web MVC, you can easily see the similarities to Springs Handler Interceptor.
Gradle
As mentioned before, Grails 3 uses Gradle instead of Gant as build system. Gradle is used for tasks like compilation, running tests and packaging the application.
When a Grails command like grails clean is executed, the job is delegated to the corresponding Gradle task (e.g. gradle clean). The Gradle-Wrapper shipped with Grails 3 is used for this.
If you want to use a local installation of Gradle you can execute the Gradle task directly with your own Gradle version. Gradle 2.2 or newer is recommended.
The following table shows Grails commands and their corresponding Gradle tasks:
| Grails command | Gradle Task |
| clean | clean |
| compile | classes |
| package | assemble |
| run-app | run |
| test-app | test |
| war | assemble |
BuildConfig.groovy from previous Grails versions has been completely replaced by the Gradle configuration ( build.gradle). Third party dependencies are now defined in build.gradle:
dependencies {
compile 'org.grails.plugins:hibernate'
compile 'org.grails.plugins:cache'
compile 'org.hibernate:hibernate-ehcache'
runtime 'org.grails.plugins:asset-pipeline'
runtime 'org.grails.plugins:scaffolding'
...
}For more details, you can have a look at Dependency Management Guide in the Gradle documentation.
Profiles
Whenever you run the create-app command Grails 3 will use a Profile to create a new app.
A Profile encapsulates project structure, commands, templates and plugins. By default Grails 3 uses the web Profile, which creates an app like shown in the screenshot above.
To create a project with a different Profile, you can use the --profile parameter:
grails create-app myapp --profile=web-plugin
Grails 3 comes with three different Profiles:
- web for standard Grails web applications
- web-plugin for web application plugins
- web-micro a minimal micro service application
Short summary
Grails 3 comes with major changes. The code basis changed to Spring Boot, Gant was replaced with Gradle, existing features were reimplemented using Traits and new features like Profiles and Interceptors were added.
With all those changes it can become quite challenging to upgrade an existing Grails 2.x application to Grails 3 (all Plugins need to be updated first). If you plan to Upgrade to Grails 3, you should have a look at the Grails 3 upgrade guide.
| Reference: | What’s new in Grails 3 from our JCG partner Michael Scharhag at the mscharhag, Programming and Stuff blog. |
muy buen aporte.gracias !
Plugins are now in build.gradle. However, all is not straightforward. I can’t get the aws-sdk plugin to install from the new repository, even though I’ve told gradle about the new repository. The plugin is not found under any name I can think of – aws-sdk, grails-aws-sdk. A mention of how plugins now work would be welcome.