warcommand creates a Web Application Archive (WAR) file which can be deployed on any Java EE compliant application server.
grails war grails test war grails -Dgrails.env=staging war
grails [environment]* war [filename]* [arguments]*
filename- The path and name to use in place of the default
nojars- Packages the WAR with no jar files. Used for shared deployment
StatusFinal- When the WAR file has been created
warcommand creates a web application archive (WAR) file using the application name and version number. The
warcommand is different from most commands since it runs in the production environment by default instead of development, but like any script the environment can be specified using the standard convention:
You can also specify a custom environment:
grails test war grails dev war grails prod war grails war /foo/bar/mywar.war grails war --nojars
Once the WAR has been created you can deploy it to your container using its standard WAR deployment process.
grails -Dgrails.env=UAT war