Groovy Cookbook

Why "grails package" executes Config.groovy file?

This blog post is inspired by one of my recent Stack Overflow answers to following question: Grails: why is the Config.groovy file executed during compilation?. Here I’m going to show you step by step what makes grails package command executing Config.groovy script and how I’ve managed to find the answer to that question.

Grails 2.4 configuration files

According to following Grails 2.4 documentation:

For general configuration Grails provides two files:

  • grails-app/conf/BuildConfig.groovy

  • grails-app/conf/Config.groovy

Both of them use Groovy’s ConfigSlurper syntax. The first, BuildConfig.groovy, is for settings that are used when running Grails commands, such as compile, doc, etc. The second file, Config.groovy, is for settings that are used when your application is running. This means that Config.groovy is packaged with your application, but BuildConfig.groovy is not. Don’t worry if you’re not clear on the distinction: the guide will tell you which file to put a particular setting in.

After reading such a documentation you could run into an assumption, that no matter what you put into Config.groovy file it will get executed while running application only. Unfortunately - this is not true.

Packaging Grails application

Let’s investigate together what happens when we call grails package command. Every Grails command has a Groovy script associated. Those scripts are provided with Grails distribution. package command is represented by following Groovy script:

 * Copyright 2004-2005 the original author or authors.
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * See the License for the specific language governing permissions and
 * limitations under the License.

 * Gant script that packages a Grails application (note: does not create WAR).
 * @author Graeme Rocher
 * @since 0.4

if (getBinding().variables.containsKey("_grails_package_called")) return
_grails_package_called = true

includeTargets << grailsScript("_GrailsCompile")
includeTargets << grailsScript("_PackagePlugins")

target(createConfig: "Creates the configuration object") {
    if (!binding.variables.containsKey("configLoaded")) {
        config = projectPackager.createConfig()
        configLoaded = true

target(packageApp : "Implementation of package target") {
    grailsConsole.updateStatus "Packaging Grails application"
    profile("compile") {

    projectPackager.classLoader = classLoader

    try {
        config = projectPackager.packageApplication()
    catch(e) {
        grailsConsole.error "Error packaging application: $e.message", e
        exit 1




target(configureServerContextPath: "Configuring server context path") {
    serverContextPath = projectPackager.configureServerContextPath()

target(startLogging:"Bootstraps logging") {

target(generateWebXml : "Generates the web.xml file") {

target(packageTlds:"packages tld definitions for the correct servlet version") {

recompileCheck = { lastModified, callback ->
 // do nothing, here for compatibility

When you run grails package Grails executes target packageApp defined in line 38. In line 48 Grails uses GrailsProjectPackager.packageApplication() that does the packaging. Inside this method there is a call to a createConfig() private method that in line 345 delegates parsing of a configuration file to a ConfigSlurper.parse(configClass) method:

config = configSlurper.parse(configClass)

ConfigSlurper does several things, but there is one line of code we are interested the most:

This is our game changer. There is one thing worth mentioning here as well. Config.groovy is compiled to a Java class that extends groovy.lang.Script class. Basically all Groovy scripts are represented that way in the bytecode - this class is simply a wrapper that provides main method that is executed by JVM. That’s why ConfigSlurper.parse(Script script, URL location) is used to parse Config.groovy file.

Side effects

There is only one major side effect of this situation - expect that any business logic inside Config.groovy file will be executed. This is not a problem in most cases, because this file is used mostly for a assigning values to a variables we can access with grailsApplication.config reference. But if you put something like

println "Lorem ipsum dolor sit amet"

in the end of Config.groovy file, expect to see something like this when you package your Grails application:

|Loading Grails 2.4.5
|Configuring classpath
|Environment set to development
|Packaging Grails application
|Compiling 10 source files

|Compiling 107 source files

|Compiling 8 source files
.....Lorem ipsum dolor sit amet
...................Lorem ipsum dolor sit amet

Did you like this article?

Consider buying me a coffee