### JEnt 3ed Ant template

The Ant template consists of the following files:

- `build.xml`: The main project buildfile.
- `build.properties`: The build properties, with defaults
- `as-generic-config.xml`: A set of generic app server target definitions
- `as-jboss-config.xml`: A set of target definitions for JBoss
- `jfarley-build.properties`: Example of a properties override file
- `jfarley-as-config.xml`: App server config file specified by the sample user properties file

The `build.xml` file is specific to a particular project, naturally. It can be modified as-needed to suit a particular project. It imports properties first from a user-owned properties file (if present), then from the default `build.properties` file. It also imports a set of enterprise tasks from an application server target definition file, as specified in the `build.properties` file. If no user property overrides are used, the `build.xml` file loads `as-generic-config.xml`, which has minimal implementations of the enterprise targets. The `as-jboss-config.xml` is a full implementation of the enterprise targets for JBoss 3.2.x servers. Others can be created by copying the `as-generic-config.xml` file and altering the target definitions to suit the app server.

To test out the Ant template using the included sample code, do the following:

1. Copy the `as-jboss-config.xml` file to your own copy, and adjust the properties at the top of the file to suit your JBoss install.
2. Create your own properties file, named`<username>-build.properties`, and put it in the same directory as the `build.properties` file. `<username>` is your login name on your system. At a minimum, your properties file should set the `server.config.file` property to point to your app server target definitions file.
3. Run `ant deploy-app` and see what happens.