Care for the environment

Sencha Cmd supports the concept of environments to allow different behavior depending on the stage of your workflow. We've already mentioned that Sencha Cmd leverages the power of the Ant build system to allow customization of the process. The different environments simply define variables that are consumed by Ant and passed into the build process to enable, disable, or amend a part of the build.

You can see the default build variables by running the following command:

sencha ant .props

This produces something that includes the following code along with a million and one other variables:

[INF] [echoproperties] app.output.js=app.js
[INF] [echoproperties] app.output.js.compress=false
[INF] [echoproperties] app.output.js.enable=true
[INF] [echoproperties] app.output.js.optimize=false

Here the variable app.output.js has the value app.js.

Note

Note that build variables and configuration variables are two separate things. Configuration variables are used by Sencha Cmd as...