The name of the application.xml to put into an EAR file. This must be set (along with abuild.ear-name) for an EAR file to be generated.

The name of the EAR file, including the .ear suffix, to be generated. This must be set for an EAR file to be generated. EAR files contain any archive files in the abuild.classpath property. They do not contain JAR files in the abuild.classpath.external property.

A comma-separated list of build items from which hooks should be loaded. For details about using hooks, see Chapter 19, Java Hooks and Code Generators.

The name of the JAR file, including the .jar or other archive suffix, to be created by this build item. This must be set in order for a JAR file to be generated.

If specified, the value of this property will be used for the source attribute of the javac task. Otherwise, the value will come from the abuild.java-target-version if set or from the Java environment used to run ant if not.

If specified, the value of this property will be used for the target attribute of the javac task. If abuild.java-source-version is not set and this property is, then this property's value will also be used to set the source attribute of the javac task.

This property contains the name of the class that implements this build item's junit test suite. It must be set in order for the test target to attempt to run a junit test suite.

The name of a local build file, specified relative to the build item's directory, that will be imported by ant. It may contain additional properties that can't be specified in a property file, resource collections, or even additional targets. If you are using this too often, please consider whether a build item hooks file should be used instead, or whether there is some functionality that is missing from the core abuild ant framework code.

The name of a class, if any, that implements main. Setting this property causes the Main-Class attribute to be set in the manifest file. It also influences generation of the wrapper script if abuild.wrapper-name is set.

If set, ant runtime libraries will be included in the compilation classpath. This can be useful for compiling custom ant tasks.

If this and abuild.local-buildfile are both set, abuild will attempt to run hooks from the local build file as well as from any hook build items.

The name of the WAR file, including the .war suffix, to be generated. This must be set for a WAR file to be generated. WAR files contain any JAR files in the abuild.classpath property. They do not contain JAR files in the abuild.classpath.external property.

The type of the WAR file, which must be either client or server. This property determines where items in abuild.classpath are copied. For client WAR files, classpath JAR files are copied into the root of the WAR file where the are accessible to clients' browsers. For server WAR files, they are copied into the WEB-INF/lib directory of the WAR file.

The name of the web.xml to put into a WAR file. This must be set (along with abuild.war-name) for a WAR file to be generated.

If this property and abuild.main-class are both set, a script by this name will be generated that will invoke the Java runtime environment to invoke this main. The script will include the classpath as determined by abuild. On Windows, the script is usable to invoke the application from a Cygwin environment, and a stand-alone batch file (that does not reference the script or require Cygwin) is generated as well.