Hi, all.
I just finished doing some non-trivial clean-up of the build process. In
general, my goal was to move as much behavior out of the build scripts
(build-turbine.bat/.sh) and into the Ant build file (build-turbine.xml). This
makes the build scripts simpler and means that functionality need only be
implemented in the build file. My personal opinion is that the build scripts
should do nothing more than set the proper classpath and launch Ant, and today's
changes follow this philosophy.
Substantive changes:
- Now uses latest Ant release (v. 1.1).
- New 'usage' target which prints the available targets. Note that this list
only includes targets that are likely to be run by an end-user; targets such as
'prepare' (which is called internally) and 'war-webmacro' (which is experimental
and likely to be subsumed by the TDK) do not appear in this list.
- New 'env' target which prints useful build environment properties, such as
'build-compiler' and 'java.class.path'. This target is called (directly or
indirectly) by every other target (except 'usage'); hopefully, this will help in
debugging user problems.
- Now loads in "global" Ant preferences from ${user.home}/.ant.properties.
(See previous message for usage details.)
- Default target now handled entirely by the Ant build file. This removes
the TARGET variable stuff from build-turbine.bat/.sh. In addition to being more
consistent with common Ant usage, this change allows you to specify multiple
targets. For instance, you can now execute 'build-turbine clean jar'.
- Location of JSDK JAR can be specified in the JSDK environment variable. No
longer necessary to edit the build script to specify its location.
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
