Two-stage build process - dist & deploy

[GoogleCodeExporter]

At the moment the build does everything: compile jars, configure eXist and
store the initial files in the database.

Instead we need two steps:

1. Build distribution including jar & swf (both built automatically),
assets and config files. This distribution will contain everything needed
to deploy Transcript Studio (both the client (Flex) app and the server
(XQuery)) and configure eXist. So this will not include source files. It
will not only generate a "dist" folder but also ZIP and TAR.GZ files
representing that distribution.

2. Deploy - configure eXist (Saxon Jars and config file modifications).
Store relevant files (assets, xquery, xslt) in the database. This will be
run as install.bat or install.sh and is included in the distribution. It
takes all its files from the distribution built in the first step.

Original issue reported on code.google.com by mjc1...@gmail.com on 29 Jan 2009 at 5:34

[GoogleCodeExporter]

Done. r140, r141, r142, r145, 151.

So now we can send a file like: transcriptstudio-0.9.0b1.zip by email.

The receiver just needs to unzip it and run install.bat or install.sh. This 
only does
the eXist side of things. The user would have to copy the bin folder 
(containing the
SWF) to where he desires.

Maybe in future we should also generate a zip file with just the SWF (and 
assets)
since far more people might want to install the SWF than configure a new eXist 
database.

Original comment by mjc1...@gmail.com on 29 Jan 2009 at 5:38

• Changed state: Fixed
• Added labels: Type-Enhancement, Priority-Low