List of Figures

 

Chapter 1. Introducing Ant

Figure 1.1. Conceptual view of a build file. The project encompasses a collection of targets. Inside each target are task declarations, which are statements of the actions Ant must take to build that target. Targets can state their dependencies on other targets, producing a graph of dependencies. When executing a target, all its dependents must execute first.

Chapter 2. A first Ant build

Figure 2.1. The XML Representation of a build file is a tree: the project at the root contains one target, which contains two tasks. This matches the Ant conceptual model: projects contain targets; targets contain tasks.

Figure 2.2. The directory layout for our project—keeping source separate from generated files. The shaded directories and files are created during the build.

Figure 2.3. Once you add dependencies, the graph of targets gets more complex. Here clean depends upon init; archive depends on compile, and, indirectly, init. All of a target’s dependencies will be executed ahead of the target itself.

Figure 2.4. Our build file hosted under Eclipse. Consult Appendix C for the steps needed to do this.

Chapter 4. Testing with JUnit

Figure 4.1. UML diagram of the core of our diary. Interfaces and classes in grey are those of the Java libraries. We’re going to assume they work and not test them ourselves.