Currently, Sencha is part of the maven build process for SSP 2.0. Eventually, the same configuration will be added to the rel-1-2-patches and rel-1-1-patches branches.
Sencha Installation
Sencha SDK Tools can be downloaded from here: http://www.sencha.com/products/sdk-tools/download/
These steps are relevant for both the automated process as well as the manual process:
2) Add the installation directory to your PATH. Will look something like:
export PATH="/Applications/SenchaSDKTools-2.0.0-beta3:$PATH"
You can validate your Sencha installation by typing the following command (should get usage information back):
%> sencha --help
GENERAL DEVELOPMENT PROCESS
Developers should note that when adding new Ext classes, it is important to edit the ssp.jsb3 file so that the new classes will be included in the minification process. This isn't currently automated.
AUTOMATED PROCESS (SSP 2.0)
Critical parts of the Sencha build to process automatically are:
An additional environment variable was added to ssp-config.properties called ssp_main_use_minifed_js.
When set to true, ssp-main.jsp will include a reference to the minified js called app-all.js
When set to false, ssp-main.jsp will include a reference to the non-minified app.js
3 additional profiles added to SSP's pom.xml
profile for calling Sencha from Windows (called WINS), profile for calling Sencha from *inux (called LINUX), and a profile for skipping the sencha build (called SKIP_SENCHA)
MANUAL PROCESS (SSP 1.1.x and SSP 1.2.x)
Eventually, the same automated configuration will be added to the 1.2.x and 1.1.x. Until then, the manual process for these versions is:
%> cd {src_root}/src/main/webapp
2) Run the sencha tool (note the dot at the end):
%> sencha build -p ssp.jsb3 -d .
3) Add the resulting files to git:
%> git add app-all.js all-classes.js