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/
...
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.
If a developer is working on a JavaScript-heavy part of the application, he would typically modify ssp-main.jsp to include app.js rather than app-all.js, hack away on the .js files in the the source tree, and copy them to the running Tomcat instance in order to see the effects of the change. This process is still proper if development is happening on the 1.1 or 1.2 branch. The 2.0 branch handles much of this due to some additional maven profiles and an additional configuration setting that properly adjusts the ssp-main.jsp file accordingly.
AUTOMATED PROCESS (SSP 2.0)
...
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 just building 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
MANUAL PROCESS FROM PERSPECTIVE OF INSTALLATION
...