Shipping the application requires Maven 2.x

1. On all systems:

$ mvn package

This generates a file called target/${artifactId}-${version}.war you can
install in any servlet container. The .war file includes all
dependencies.

2. On Unix/Linux systems with Tomcat 5.5 you can build and install the
   application also using the following instructions:

2.1 Configure the application

$ ./configure

You can supply various options that influence where the application looks
for its dependencies and where it will find its configuration and runtime
data. You can change these values from the defaults by setting them
in the environment of ./configure.

$APP              (appname}
$PREFIX           (/usr/local)

$SYSCONFDIR       ($PREFIX/etc)
$CONFDIR          ($SYSCONFDIR/$APP)

$DATAROOTDIR      ($PREFIX/share)
$DATADIR          ($DATAROOTDIR/$APP)

$SHAREDSTATEDIR   ($PREFIX/var)
$LOGDIR           ($SHAREDSTATEDIR/log/$APP)

For example, to install application in your home directory:

$ PREFIX=$HOME ./configure

2.2 Build the application

$ ./build

2.3 Install the application:

$ sudo ./install

2.4 Dependencies

Installing the application this way requires the (Debian) packages
installed, listed as the first column in file 'jars-list' in this directory.

For the compiler and the installer to find these dependencies, you will have
to supply a suitable CLASSPATH to the configure script. Example:

$ CLASSPATH=/usr/share/java/servlet-api.jar:/usr/share/java/log4j-1.2.jar:......

Using the following command, you can generate the CLASSPATH value:

$ perl mkclasspath < jars-list

To use it for ./configure:

$ CLASSPATH=$(perl mkclasspath < jars-list) ./configure