We intend to use Grails in our company, however we face one technical
difficulty with it. We have production streams dev->test->prod that require
that we use the same WAR from dev to prod. Only external properties files
and the database are allowed to change from one environment to the other.
Our difficulty comes from the fact that the target environment (dev, test,
prod, ...) is specified by Grails inside the WAR file, in the
application.properties, using the grails.env parameter. That prevents from
using a "test" war in the "production" environment for example.
Is there a way, to ignore this grails.env parameter (or to bypass the
embedded application.properties file) and specify it elsewhere, so that we
could still use the same WAR in all our environments? Any idea is welcome :)
Xavier de Labouret
Online Multimedia - Etudes & Methodes