• First go to the website and download ant.
• Unzip it to a directory.
• Then add the bin directory to the path variable.
• Create and set the ANT_HOME environment variable.
• Make sure you have JAVA_HOME set to the jdk also.

<project name="sample" default="run" basedir=".">



  <description>

    Build for sample program.

  </description>



  <!-- contains build number and other information -->

  <property file="sampleProgramInfo.properties" />



  <property name="src.dir" value="./src" />

  <property name="build.dir" value="./build" />

  <property name="dist.dir" value="./dist" />



  <!--

	cleans all directories except the source

  -->

  <target name="clean">



    <delete dir="${build.dir}" />

    <delete dir="${build.dir}/build_docs" />

    <delete dir="$  ist.dir " />

    <delete dir="$  ist.dir /src" />

    <delete dir="$  ist.dir /build" />



    <mkdir dir="${build.dir}" />

    <mkdir dir="${build.dir}/build_docs" />

    <mkdir dir="$  ist.dir " />

    <mkdir dir="$  ist.dir /src" />

    <mkdir dir="$  ist.dir /build" />

  </target>



  <!-- Compiles the source to the build -->

  <target name="compile">



    <!-- update or create build info -->

    <propertyfile file="sampleProgramInfo.properties"

	comment="Build Statistics for sample program">

      <entry key="programName" type="string"

	default="sample program" />

      <entry key="version" type="string" default="1.0" />

      <entry key="firstBuildDate" type="date"

	default="now" />

      <entry key="currentBuildDate" type="date"

	default="now" value="now" />

      <entry key="buildNumber" type="int" default="0"

	operation="+" />

    </propertyfile>



    <javac srcdir="${src.dir}" destdir="${build.dir}" />

  </target>



  <!-- move all non source code files to build this

	could be program resources -->

  <target name="move" depends="compile">

    <copy todir="${build.dir}">

      <fileset dir="${src.dir}">

	<exclude name="**/*.java" />

      </fileset>

    </copy>



    <copy todir="${build.dir}/build_docs"

	file="sampleProgramInfo.properties" />

    <copy todir="${build.dir}/resources"

	file="sampleProgramInfo.properties" />

    <copy todir="${build.dir}/build_docs"

	file="build.xml" />

  </target>



  <!-- create a distribution of the whole program

	including the source. One thing that can be

	done after this is creating a zip file and md5.

  -->

  <target name="dist" depends="move">



    <copy todir="$  ist.dir /src">

      <fileset dir="${src.dir}" />

    </copy>



    <copy todir="$  ist.dir /build">

      <fileset dir="${build.dir}" />

    </copy>



  </target>



  <!-- runs the program -->

  <target name="run" depends="dist">

    <exec dir="${build.dir}" executable="java">

      <arg line="-classpath '.' SampleProgram"/>

    </exec>

  </target>

</project>

-/SampleProgram

--+--/build.xml

--+--/src

--+--/build

--+--/dist

Apache Ant is a Java-based build tool. In theory, it is kind of like Make, but without Make's wrinkles.

Why another build tool when there is already make, gnumake, nmake, jam, and others? Because all those tools have limitations that Ant's original author couldn't live with when developing software across multiple platforms. Make-like tools are inherently shell-based -- they evaluate a set of dependencies, then execute commands not unlike what you would issue in a shell. This means that you can easily extend these tools by using or writing any program for the OS that you are working on. However, this also means that you limit yourself to the OS, or at least the OS type such as Unix, that you are working on.

Makefiles are inherently evil as well. Anybody who has worked on them for any time has run into the dreaded tab problem. "Is my command not executing because I have a space in front of my tab!!!" said the original author of Ant way too many times. Tools like Jam took care of this to a great degree, but still have yet another format to use and remember.

Ant is different. Instead of a model where it is extended with shell-based commands, Ant is extended using Java classes. Instead of writing shell commands, the configuration files are XML-based, calling out a target tree where various tasks get executed. Each task is run by an object that implements a particular Task interface.

Granted, this removes some of the expressive power that is inherent by being able to construct a shell command such as `find . -name foo -exec rm {}`, but it gives you the ability to be cross platform -- to work anywhere and everywhere. And hey, if you really need to execute a shell command, Ant has an task that allows different commands to be executed based on the OS that it is executing on.

//File Name: HelloWorld.java



public class HelloWorld  {



	public static void main(String args[])  {



		System.out.println("Hello World!");

	}

}

javac HelloWorld.java

java HelloWorld

|x-x-x-x-x-x-|

|o--o--o---o-|

|x-x-x-x-x-x-|

|o--o--o---o-|

|o----o---o--|

|x-x-x-x-x-x-|

|o--o--o---o-|

|o----o---o--|

|x-x-x-x-x-x-|

|o--o--o---o-|

|o-oo-o--oo--|

After training, Bush kept flying, racking up hundreds of hours in F-102 jets. As he did, he accumulated points toward his National Guard service requirements. At the time, guardsmen were required to accumulate a minimum of 50 points to meet their yearly obligation.

[...]

...Bush earned 253 points in his first year, May 1968 to May 1969

Bush earned 340 points in 1969-1970. He earned 137 points in 1970-1971. And he earned 112 points in 1971-1972...

• copying music
• marijauana (legal or not, good or bad)
• kerry or bush
• sacrifice
• new links from rss feeds I like
• html basics (give good sites for learning html)
• reason to join the Navy
• Why I'm in a band