Java[tm] Adventure Builder Reference application - Version 1.0.4> Building the Demo

Java^TM Adventure Builder Refernce application - Version 1.0.4 > Building the Demo

Asant and Ant

We use script asant, which is located in the J2EE 1.4 SDK bin directory, to build the source code of this application. asant is a wrapper around Ant which is a Java-based build tool like make, which has been developed under the auspices of the Apache Software Foundation. Ant version 1.5.3 and 1.6 beta 1 may also be used to build and deploy the applications.

Note: The Java^TM Adventure Builder Reference application bundle comes with pre-built binaries. To deploy these binaries and avoid building the application, consult the installation instructions.

Build Adventure Builder Reference application v1.0.4

This section explains how to build the application binaries for the Java^TM Adventure Builder Reference application. Building all the application binaries and performing other tasks with Ant involves invoking asant from <adventure.home>/project directory of the demo installation.

Before building the application, you need to configure the <adventure.home>/project/build.properties file to match your enviroment. You need to set the following properties:

Property Name	Description	Examples
j2ee.home	The absolute path to the directory where J2EE SDK is installed	c:\j2sdkee1.4 (on Windows) or /home/mydir/j2sdkee1.4 (on Unix)

Note: On Windows, while writing the paths in the build.properties files, you need to escape the "\" properly by using "\\" instead. For example, to set j2ee.home to c:\j2sdkee1.4, the entry in the properties file is j2ee.home=c:\\j2sdkee1.4.

To build the application binaries on Unix, open a shell prompt and enter these commands:

cd <adventure.home>/project
asant [argument]

To build the application binaries on Windows, open a shell prompt and enter these commands:

cd <adventure.home>\project
asant [argument]

For the above command to work, your PATH environment variable must have been set as explained in the installation instructions and the ANT_HOME environment variable, if any, should not point to any other version of ant that migh be on your system. When asant is invoked without any arguments, all the application binaries are built. The binaries are placed in the following folders:

<adventure.home>/project/apps/consumerwebsite/build/consumerwebsite.ear

<adventure.home>/project/apps/opc/build/opc.ear

<adventure.home>/project/apps/bank/build/bank.ear

<adventure.home>/project/apps/activitysupplier/build/activitysupplier.ear

<adventure.home>/project/apps/airlinesupplier/build/airlinesupplier.ear

<adventure.home>/project/apps/lodgingsupplier/build/lodgingsupplier.ear

The following table lists possible arguments when invoking asant :

Option	Purpose
`core`	Builds everything. (This is the default build target.)
`cleanall`	Cleans out the build output directories.
`deploy-apps`	Deploys the application binaries.