You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2018. It is now read-only.
roblarsen edited this page Feb 4, 2013
·
1 revision
You can define 'environments' for the build process. The original targets still exist, and run the same functions, however each target now has a prod, test and dev environment too.
Here is how the environments work:
dev - Increases build number, cleans and copies the build and optimises any images if the target originally did
test - Runs everything that the original target did, however it does not strip the console.log or profiling parts
prod (default) - Runs everything the original target did
To run it you simply use ant <target> -Denv=<environment>
ant build -Denv=dev
If you don't provide the env variable it will use the production environment