Version 1.2 - 2000/07/26
+Version 1.2 - 2000/07/27
If there is a property called "builddir" with the value "build", then this could be used in an attribute like this: "${builddir}/classes". This is resolved as "build/classes".
-A project can have a set of tokens that might be automatically expanded if -found when a file is copied, when the filtering-copy behavior is selected in the -tasks that support this. These might be set in the buildfile -by the filter task.
-Since this can be a very harmful behavior, the tokens in the files must -be of the form @token@ where token is the token name that is set -in the filter task. This token syntax matches the syntax of other build systems -that perform such filtering and remains sufficiently orthogonal to most -programming and scripting languages, as well with documentation systems.
-Note: in case a token with the format @token@ if found in a file but no -filter is associated with that token, no changes take place. So, no escaping -method is present, but as long as you choose appropriate names for your tokens, -this should not cause problems.
--+<project name="foo" default="dist" basedir="."> - <target name="init"> - <tstamp/> - <property name="build" value="build" /> - <property name="dist" value="dist" /> - <filter token="version" value="1.0.3" /> - <filter token="year" value="2000" /> - </target> ++<project name="MyProject" default="dist" basedir="."> - <target name="prepare" depends="init"> + <!-- set global properties for this build --> + <property name="src" value="." /> + <property name="build" value="build" /> + <property name="dist" value="dist" /> + + <target name="prepare"> + <!-- Create the time stamp --> + <tstamp/> + <!-- Create the build directory structure used by compile --> <mkdir dir="${build}" /> </target> <target name="compile" depends="prepare"> - <javac srcdir="${src}" destdir="${build}" filtering="on"/> + <!-- Compile the java code from ${src} into ${build} --> + <javac srcdir="${src}" destdir="${build}" /> </target> <target name="dist" depends="compile"> + <!-- Create the ${dist}/lib directory --> <mkdir dir="${dist}/lib" /> - <jar jarfile="${dist}/lib/foo${DSTAMP}.jar" - basedir="${build}" items="com"/> + + <!-- Put everything in ${build} into the MyProject-${DSTAMP}.jar file --> + <jar jarfile="${dist}/lib/MyProject-${DSTAMP}.jar" basedir="${build}" /> </target> - <target name="clean" depends="init"> + <target name="clean"> + <!-- Delete the ${build} and ${dist} directory trees --> <deltree dir="${build}" /> <deltree dir="${dist}" /> </target> </project> -+
A project can have a set of tokens that might be automatically expanded if +found when a file is copied, when the filtering-copy behavior is selected in the +tasks that support this. These might be set in the buildfile +by the filter task.
+Since this can be a very harmful behavior, the tokens in the files must +be of the form @token@ where token is the token name that is set +in the filter task. This token syntax matches the syntax of other build systems +that perform such filtering and remains sufficiently orthogonal to most +programming and scripting languages, as well with documentation systems.
+Note: in case a token with the format @token@ if found in a file but no +filter is associated with that token, no changes take place. So, no escaping +method is present, but as long as you choose appropriate names for your tokens, +this should not cause problems.
+You can specify PATH and CLASSPATH variables using both ":" and ";" as separator characters, Ant will