How do you build multiple files of the same app?

[bmacdon1]

I am just wondering what you guys did to generate the different extjs files. Did you use multiple properties files or is there a configuration I can use?

Example of built files:
ext-all.js
ext-all-debug.s
ext-all-debug-w-comments.js

[aw1zard2]

sencha -sdk ext-4.2.2 compile exclude -namespace Ext.ux,Ext.chart,Ext.flash,Ext.rtl 
and include -namespace Ext.ux.IFrame 
and -debug=false concat myext-debug-w-comments.js 
and -debug=false concat -strip myext-debug.js 
and -debug=true concat -strip myext-dev.js 
and -debug=false concat -strip -yui myext-all.js 

The -strip removes all comments.
The -debug=false removes all the warn/error messages ext-dev produces.

This is just one example of how to use it.
It is close to what I used at my company.

[mitchellsimoens]

The -debug=false removes all the warn/error messages ext-dev produces.

You may see code around that looks like this:

//<debug>
.... code here
//</debug>

Anything within the //<debug> and //</debug> will be stripped out. I use this in my apps quite a bit to override settings for local dev and the build will automatically remove them for deployment to prod so it's like automation for local dev to prod settings. Also in extensions I built, if say an argument is missing or wrong type I use it to give out warnings so someone would know that they did something wrong (if they look at the console), this is basically what the framework does is if something isn't right it logs/errors out but is wrapped in the debug comments.

[bmacdon1]

sencha -sdk ext-4.2.2 compile exclude -namespace Ext.ux,Ext.chart,Ext.flash,Ext.rtl 
and include -namespace Ext.ux.IFrame 
and -debug=false concat myext-debug-w-comments.js 
and -debug=false concat -strip myext-debug.js 
and -debug=true concat -strip myext-dev.js 
and -debug=false concat -strip -yui myext-all.js 

The -strip removes all comments.
The -debug=false removes all the warn/error messages ext-dev produces.

This is just one example of how to use it.
It is close to what I used at my company.

What about running it through the test.properties / production.properties file?