Ringlord Technologies Products

AntBuilder

AntBuilder gathers from you a few items of information about your project, and then builds from those an Ant build.xml file with the following uses:

ant -p
Displays all the targets you can use (Ant will do this for any of its scripts; AntBuilder merely ensures that the right targets are visible this way);
ant all
Builds everything from a clean start;
ant compile
Compiles what needs changing;
ant jar
Builds the JAR for your project;
ant jar4, ant jar5, ant jar6, and jar7
Builds the JAR for your project based on a particular target (Java 1.4, Java 1.5, Java 1.6, or Java 1.7);
ant docs
Builds the JavaDoc for your project;
ant dist
Builds a distributable package containing your software and, optionally, source code, documentation, and miscellaneous files;
ant gitlog
Generates a changelog from the output of the 'git log -M --namestatus' command.

AntBuilder saves your settings in a hidden file (.antbuildrc) in the current directory and reads them again when you decide to change what the build.xml file contains.

AntBuilder writes the build.xml file as _build.xml, requiring you to rename it or copy it over your existing build.xml file; it will never destroy your existing build.xml

The build.xml that AntBuilder generates can either reference external libraries in the Class-Path field of the JAR's manifest, or repackage (extract/transfer) the contents of libraries into your own JAR for delivery of a single JAR without external dependencies.

Description:A Java tool to construct a build.xml file for Ant. If nothing else, this is a great way to get started with a project. We use this all the time!
Version:1.3
License:Free as in Beer
Requirements:Java 1.5+
Shell:java -jar antbuilder.jar
Download:antbuilder.jar (20.5KiB)
Documentation:antbuilder.odt (32.4KiB)
antbuilder.pdf (54.8KiB)

All content is copyright © Ringlord Technologies unless otherwise stated. We do encourage deep linking to our site's pages but forbid direct reference to images, software or other non-pages stored here; likewise, do not embed our content in frames or other constructs that may mislead the reader about the content ownership. Play nice, yes?