Using Ant

---

Why Ant Is Here (and What You Actually Need to Know)

Ant is a build tool. In this course, its one job is to handle the repetitive mechanics of turning your Java source code into a running, deployable application. It compiles your .java files, bundles them into .jar files, generates documentation, and cleans things up between builds.

Here is the important part: you are not expected to learn Ant itself. Ant was not part of your intro Java course, and that is completely fine. You do not need to memorize how it works internally or understand every line of its configuration. Think of Ant as a helper that has already been set up to work for you. When you run a command like ant build_labs, Ant quietly handles all the steps behind the scenes so that you can focus on writing Java instead of managing the build process by hand.

What you do need is a general sense of what Ant is doing for you and which command to run for each task. That is it. Everything below gives you exactly that.

You do not have to master Ant to succeed in this course. You just need to know that it is working for you, and which target to run.

How Ant Works (the short version)

When you run ant in your terminal, it looks for a file called build.xml in your current directory. That file is the recipe. It defines targets (named tasks like compile_labs or build_analyzer) and tells Ant where your source files are, where compiled output should go, and what classpath to use.

For this course, the build.xml has already been written and configured for you. You do not need to edit it, and you should not. Your job is simply to run the correct target for what you are trying to do.

your-projects-directory/
├── build.xml          ← Ant reads this (already set up for you)
├── src/               ← your .java source files go here
├── classes/           ← compiled .class files go here (generated)
└── lib/               ← .jar files go here (generated by build targets)

Curious About build.xml? Explore Away, Just Do Not Change It

You are welcome, and even encouraged, to open build.xml and look around if you are curious about how the build works. Reading it is a great way to see what a real-world build file looks like, and you are always free to ask questions about anything you find in it.

Just please do not modify it. The targets are carefully wired together so that compiling, building jars, generating docs, and deploying all work correctly. Changing something in build.xml can quietly break those targets, and then commands that used to "just work" will start failing in confusing ways. So explore it, learn from it, and ask about it, but leave the file itself alone.

Ant Targets

Here are the ant targets we will be using. For each one, you just run the command and Ant does the work. We will tell you in each lab and project which targets to use and in a few weeks you'll having much of this memorized.

Category	Command	Description
General	ant clean	Clears all compiled code in preparation for a full rebuild.
General	ant init	Creates all directories needed for building your projects.
General	ant jdoc	Generates Javadoc for all your projects.
Analyzer	ant compile_analyzer	Only compiles the analyzer app (no jar). Use this while developing to check compilation.
Analyzer	ant build_analyzer	Build & compiles the analyzer, then creates analyzer.jar in lib/. Run the app from this jar via runanalyzer.sh.
Labs	ant compile_labs	Only compiles all labs.
Labs	ant build_labs	Builds & complies the labs jar so you can run them.