+
+Compiles a Java source tree.
+
+The source and destination directory will be recursively scanned for Java
+source files to compile. Only Java files that have no corresponding class file
+or where the class file is older than the java file will be compiled.
+
+Note: Ant uses only the names of the source and class files to find
+the classes that need a rebuild. It will not scan the source and therefor
+will have no knowledge about nested classes, classes that are named different
+from the source file and so on.
+
+The directory structure of the source tree should follow the package
+hierarchy.
+
+It is possible to refine the set of files that are being compiled/copied.
+This can be done with the includes, includesfile, excludes, excludesfile and defaultexcludes
+attributes. With the includes or includesfile attribute you specify the files you want to
+have included by using patterns. The exclude or excludesfile attribute is used to specify
+the files you want to have excluded. This is also done with patterns. And
+finally with the defaultexcludes attribute, you can specify whether you
+want to use default exclusions or not. See the section on directory based tasks, on how the
+inclusion/exclusion of files works, and how to write patterns.
+
+It is possible to use different compilers. This can be selected with the
+"build.compiler" property or the compiler attribute. Here are the choices:-
+
+ - classic (the standard compiler of JDK 1.1/1.2) - javac1.1 and
+ javac1.2 can be used as aliases
+ - modern (the standard compiler of JDK 1.3/1.4) - javac1.3 and
+ javac1.4 can be used as aliases
+ - jikes (the Jikes
+ compiler)
+ - jvc (the Command-Line Compiler from Microsoft's SDK for Java /
+ Visual J++) - microsoft can be used as an alias
+ - kjc (the kopi
+ compiler)
+ - gcj (the gcj compiler from gcc)
+ - sj (Symantec java compiler) - symantec can be used as an alias
+ - extJavac (run either modern or classic in a JVM of its own)
+
+For JDK 1.1/1.2, classic is the default. For JDK 1.3/1.4, modern is the default.
+If you wish to use a different compiler interface than those
+supplied, write a class that implements the CompilerAdapter interface
+(package org.apache.tools.ant.taskdefs.compilers). Supply the full
+classname in the "build.compiler" property.
+
+The fork attribute overrides the build.compiler setting and expects
+a JDK1.1 or higher to be set in java.home.
+
+This task will drop all entries that point to non-existent
+files/directories from the CLASSPATH it passes to the compiler.
+
+Windows Note:When the modern compiler is used
+in unforked mode on Windows, it locks up the files present in the
+classpath of the <javac> task, and does not release them. The side
+effect of this is that you will not be able to delete or move
+those files later on in the build. The workaround is to fork when
+invoking the compiler.
+
+
+
+
+ <javac srcdir="${src}"
+ destdir="${build}"
+ classpath="xyz.jar"
+ debug="on"
+ />
+compiles all .java files under the ${src}
+directory, and stores
+the .class files in the ${build} directory.
+The classpath used contains xyz.jar, and debug information is on.
+
+ <javac srcdir="${src}"
+ destdir="${build}"
+ fork="true"
+ />
+compiles all .java files under the ${src}
+directory, and stores the .class files in the
+${build} directory. This will fork off the javac
+compiler using the default javac executable.
+
+ <javac srcdir="${src}"
+ destdir="${build}"
+ fork="java$$javac.exe"
+ />
+compiles all .java files under the ${src}
+directory, and stores the .class files in the
+${build} directory. This will fork off the javac
+compiler using the executable named java$javac.exe. Note
+that the $ sign needs to be escaped by a second one.
+
+ <javac srcdir="${src}"
+ destdir="${build}"
+ includes="mypackage/p1/**,mypackage/p2/**"
+ excludes="mypackage/p1/testpackage/**"
+ classpath="xyz.jar"
+ debug="on"
+ />
+compiles .java files under the ${src}
+directory, and stores the
+.class files in the ${build} directory.
+The classpath used contains xyz.jar, and debug information is on.
+Only files under mypackage/p1 and mypackage/p2 are
+used. Files in the mypackage/p1/testpackage directory are excluded
+from compilation.
+
+ <javac srcdir="${src}:${src2}"
+ destdir="${build}"
+ includes="mypackage/p1/**,mypackage/p2/**"
+ excludes="mypackage/p1/testpackage/**"
+ classpath="xyz.jar"
+ debug="on"
+ />
+
+is the same as the previous example, with the addition of a second
+source path, defined by
+the property src2. This can also be represented using nested
+<src> elements as follows:
+
+ <javac destdir="${build}"
+ classpath="xyz.jar"
+ debug="on">
+ <src path="${src}"/>
+ <src path="${src2}"/>
+ <include name="mypackage/p1/**"/>
+ <include name="mypackage/p2/**"/>
+ <exclude name="mypackage/p1/testpackage/**"/>
+ </javac>
+
+Note: If you are using Ant on Windows and a new DOS window pops up
+for every use of an external compiler, this may be a problem of the JDK you are using.
+This problem may occur with all JDKs < 1.2.
+
+Note: If you wish to compile only source-files located in some packages below a
+common root you should not include these packages in the srcdir-attribute. Use include/exclude-attributes
+or elements to filter for these packages. If you include part of your package-structure inside the srcdir-attribute
+(or nested src-elements) Ant will start to recompile your sources every time you call it.
+
+
+
+
-
-
- #if( $project.logo )
-
- #set( $alt = $project.logo )
- #set( $home = $project.attribute("href") )
- #set( $src = $project.logo.attribute( "href" ) )
-
- ## PROJECT LOGO
-
-