Include tasks for compiling the project, generating javadoc, and packaging all Using Ant removes one burden by automating the build process. propertyfileSpecifies using properties from this These are the primary Ant command-line options: Temporary build directory is also created. *.class files in the distribution directory. (subdirectory of the current directory) and places the generated The following simple example (tested with Antġ.4.1) compiles the *.java files in the source directory In this configuration file are the instructions Ant follows. The configuration XML file, usually build.xml, is the key to usingĪnt. Javadoc documentation and even place the whole project into a single JAR file, Script that comes with Ant works correctly with Cygwin, but you might have toįollow these three steps to get started with Ant:Īfter these steps, compiling an application with Ant is as simple as issuing For example, JBuilder automatically recognizes Ant build files
Many popular Java Integrated Development Environments (IDEs) have Antįunctionality.
With the SDK 1.4, you don't have toĭo anything because JAXP is included (see Must have a Java API for an XML Processing (JAXP)compliant XML parser
You can get the binary edition of Ant from the Ant Web page at Using Ant can ensure that only the essential files are "distributed" Make sure none of these files find their way to your evaluator's screen. Will likely use test classes, backup source files, and tool configuration files. Avoid including working or temporary files in your project submission.