How to set up an environment for Apache Ant?
Unzip the zip file to a convenient location c://folder. using Winzip, winRAR, 7-zip or similar tools. Create a new environment variable called ANT_HOME that points to the Ant installation folder, in this case c://apache-ant-1.8.2-bin folder. Add the path to the Apache Ant batch file to the PATH environment variable.
Table of Contents
How does the Ant build and release task work?
(Required) Specify a comma-separated list of relative paths from the Ant build file to the directories that contain your .class files, archive files (such as .jar and .war). Code coverage is reported for class files present in directories. Directories and files are searched recursively for class files.
How are variables set in an Ant build?
Alternatively, built-in variables are already set as environment variables during build and can be passed directly (for example, -DcollectionIdAsEnvVar=%SYSTEM_COLLECTIONID% ). (Optional) Target(s) for Ant to run for this build.
What is the name of the build file in ant?
By default, Ant uses build.xml as the name of a build file, so our .//build.xml would be: Looking at the build file, we’ll see some similar steps between Ant and Java-only commands:
Where do I find the ant installation folder?
Unzip the zip file to a convenient location c://folder using Winzip, winRAR, 7-zip or similar tools. Create a new environment variable called ANT_HOME that points to the Ant installation folder. In this case, it is the c://apache-ant-1.10.9-bin folder.
The Export Workspace Metadata check box controls whether a workspace metadata file is created. This file allows you to run Ant scripts on a remote machine that does not have access to the workspace, by relativizing the absolute paths in the workspace’s .metadata directory. For more details, see the workspace metadata file above.
Where to find path variables in Ant build?
The list of path variables to specify is available on the second page of the File > Export > Workshop Build Scripts > Workshop Ant Scripts dialog.
