BuildConfig has no environment support

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

Depending on what you are trying to do, there is a workaround for this. For instance, I wanted to build the environment into my war name, so I did this:

grails.project.war.file="MyAppName.$

.war"

This would be very helpful to allow for port setting in the build config depending on environment or even the db libraries.

It would also be very helpful to allow for loading different sets of plugins for different environments

Why not using

switch (Environment.current) {
        case Environment.DEVELOPMENT:
         //...
}

as workaround?

The trouble is that the environment is not guaranteed to be known when the BuildConfig.groovy file is parsed. Therefore you can't rely on Environment.current being the correct environment.

I am sure I have seen something on the mailing list about the Dependency DSL being able to exclude plugins by environment.

Don't forget that the dependency DSL is inside a closure property and that closure is evaluated later than BuildConfig.groovy itself.

This would be very helpful to support multiple build environments - each one with different plugin dependencies (ie latest.integration, latest.release).

I would like to have different web.xml base files for different environments. Currenlty I list the web.xml.tmp location in the BuildConfig. I don't want to use my tmp for Development...only test and production. So I have to manually comment/uncomment based on my environment. Looking at the gant scripts now to try and work around this.

I'm doing like that :

//Workaround to detect grails environment
def environment = Environment.getCurrent()

if (environment == Environment.PRODUCTION){
    plugins {
            println "use plugin tomcat in env:  ${environment}"
            compile ":tomcat:1.3.7"
        }
    }else{
        plugins {
            println "use plugin tomcatnio in env:  ${environment}"
            compile ":tomcatnio:1.3.4"
        }
    }

Any news on this issue? Will it ever be possible to specify some plugin (like console) just for my development environment?

@Rodrigo That's already possible by declaring the dependency inside an 'if (Environment.current == Environment.PRODUCTION)' condition. This issue relates to the settings outside of such closures.

I was unlucky with 'Environment.current' but testing System.getProperty('grails.env') == 'production' just works for my Grails 2.2.0.