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 SDK Tools can be downloaded from here: http://www.sencha.com/products/sdk-tools/download/
Manual process still required for rel-1-2-patches and rel-1-1-patches branches:
1) Install sencha tools
2) Add the installation directory to your PATH. Will look something like:
for OSX:
export PATH="/Applications/SenchaSDKTools-2.0.0-beta3:$PATH"
export PATH="/Applications/SenchaSDKTools-2.0.0-beta3:$PATH"
for Windows (easiest to add environment variable, or set from cmd prompt):
set path=%path%;<Sencha SDK Tools Installation Dir>
You should then get usage information back from:
%> sencha --help
3) cd over to the directory with your ssp.jsb3 file:
%> cd {src_root}/src/main/webapp
4) Run the sencha tool (note the dot at the end):
%> sencha build -p ssp.jsb3 -d .
6) Add the resulting files to git:
%> git add app-all.js all-classes.js
** I never was able to successfully generate a jsb3 file automatically ('sencha create …' would either error out or hang) so I *think* you might need to edit that file by hand whenever adding new Ext classes. If you know of a good way to get that to work automatically, I'm all ears.
%> sencha --help
3) cd over to the directory with your ssp.jsb3 file:
%> cd {src_root}/src/main/webapp
4) Run the sencha tool (note the dot at the end):
%> sencha build -p ssp.jsb3 -d .
6) Add the resulting files to git:
%> git add app-all.js all-classes.js
** I never was able to successfully generate a jsb3 file automatically ('sencha create …' would either error out or hang) so I *think* you might need to edit that file by hand whenever adding new Ext classes. If you know of a good way to get that to work automatically, I'm all ears.
Also, as discussed on IRC, you don't need to do this to see every incremental change you make in a local dev environment. What I usually do is modify ssp-main.jsp to include app.js instead of app-all.js, hack on .js files in my source tree, and cp them into a running Tomcat every time I want to look at the effect of my changes. I don't generate and test the aggregated files until just before I'm ready to commit.