Hi,

I've updated the commandline option -projecthelp to output two sorted list
of targets, those with and those without a description. This way you get a
hint as to which targets are meant to be called from the outside and which
are more like internal targets, without losing the complete picture.
And ofcourse I also updated the docs :), ahum should have done that the
first time around. The patches for build.xml and buildant.xml are a first
try to use descriptions on ant itself. Could someone check to see if there
are more targets that are meant to be called directly?

A second smaller documentation change was triggered by Paul Arzul's question
on ant-user: the possibility to specify more than one target on the
commandline was not documented.

Regards,
Marcel
--- iindex.html Sat Sep 09 08:36:54 2000 +++ index.html Mon Sep 11 09:32:41 2000 @@ -99,13 +99,13 @@

To build and use ant you must have a JAXP compliant XML parser installed and available on your classpath.

- If you do not have a JAXP compliant XML parse installed, you may use the reference implementation + If you do not have a JAXP compliant XML parse installed, you may use the reference implementation available from Sun. It is available from http://java.sun.com/xml. Once installed make sure the "jaxp.jar" and "parser.jar" files are in your classpath.

- You will also need the JDK installed on your system, version 1.1 or later. + You will also need the JDK installed on your system, version 1.1 or later. -


+

Building Ant

Go to the directory jakarta-ant.

Make sure the JDK is in you path.

@@ -151,12 +151,12 @@

Advanced

There are lots of variants that can be used to run Ant. What you need is at least the following:

-

The classpath for Ant must contain ant.jar and any jars/classes +

The classpath for Ant must contain ant.jar and any jars/classes needed for your chosen JAXP compliant XML parser.

When you need JDK functionality (like a javac task, or a rmic task), then for JDK 1.1, the classes.zip file of the JDK must be added to the classpath; for JDK 1.2, tools.jar -must be added. The scripts supplied with ant, in the bin directory, will add +must be added. The scripts supplied with ant, in the bin directory, will add tools.jar automatically if the JAVA_HOME environment variable is set.

When you are executing platform specific applications (like the exec task, or the cvs task), the property ant.home @@ -170,25 +170,27 @@ another buildfile, use the commandline option -buildfile <file>, where <file> is the buildfile you want to use.

You can also set properties which override properties specified in the -buildfile (see the property task). +buildfile (see the property task). This can be done with the -D<property>=<value> option, where <property> is the name of the property and <value> the value.

-

To more options are -quiet which instructs Ant to print less +

Two more options are -quiet which instructs Ant to print less information on the console when running. The option -verbose on the other hand makes Ant print more information on the console.

-

It is also possible to specify the target that should be executed. Default -the target that is mentioned in the default attribute of the project is -used. This can be overridden by adding the target name to the end of the -commandline.

+

It is also possible to specify one or more targets that should be executed. When omitted the target that is mentioned in the default attribute of the project is +used.

+

The -projecthelp option gives a list of this projects targets. First those with a description and then those without one.

Commandline option summary:

-
ant [options] [target]
+
ant [options] [targets]
 Options:
 -help                  print this message
+-projecthelp           print project help information
 -version               print the version information and exit
 -quiet                 be extra quiet
 -verbose               be extra verbose
+-emacs                 produce logging information without adornments
 -logfile <file>        use given file for log
+-logger <classname>    the class which is to perform logging
 -listener <classname>  add an instance of class as a project listener
 -buildfile <file>      use given buildfile
 -D<property>=<value>   use value for given property
@@ -295,13 +297,14 @@
<target name="build-module-A" if="module-A-present"/>
<target name="build-own-fake-module-A" unless="module-A-present"/>
-

If no if and no unless attribute is present, the target will +

If no if and no unless attribute is present, the target will always be executed.

It is a good practice to place your tstamp tasks in a so called initialization target, on which all other targets depend. Make sure that target is always the first one in the depends list of the other targets. In this manual, most initialization targets have the name "init".

+

The optional description attribute can be used to provide a one line description of this target that is printed by the -projecthelp commandline option.

A target has the following attributes:

@@ -328,10 +331,15 @@ - + + + + +
unlessthe name of the property that must not be set in order + the name of the property that must not be set in order for this target to execute. No
descriptiona short description of this targets function.No

Tasks

A task is a piece of code that can be executed.

@@ -493,23 +501,23 @@ Required - value + value a single command line argument, can contain space characters. Exactly one of these. - line + line a space delimited list of command line arguments. - file + file The name of a file as a single command line argument. Will be replaced with the absolute filename of the file by Ant. - path + path A string that shall be treated as a PATH like string as a single command line argument. You can use ; or : as path separators and Ant will convert it to the platform's local @@ -605,7 +613,7 @@ the include patterns, and don't match the exclude patterns are used.

Patterns can be specified inside the buildfile via task attributes or nested elements and via external files. Each line of the external file -is taken as pattern that is added to the list of include or exclude +is taken as pattern that is added to the list of include or exclude patterns.

Patterns

As described earlier, patterns are used for the inclusion and exclusion. @@ -698,7 +706,7 @@ "**/CVS/*", "**/.cvsignore"

-If you do not want these default excludes applied, you may disable them with the +If you do not want these default excludes applied, you may disable them with the defaultexcludes="no" attribute.

PatternSets

Patterns can be grouped to sets and later be referenced by their id @@ -755,7 +763,7 @@ that support this feature or at the same level as target - i.e. as children of project.

PatternSets can be specified as nested -<patternset> +<patternset> elements. In addition FileSet holds an implicit PatternSet and supports the nested <include> and <exclude> elements of PatternSet directly as well @@ -921,9 +929,9 @@


AntStructure

-

Description:

+

Description:

Generates a DTD for Ant build files which contains information -about all tasks currently known to Ant.

+about all tasks currently known to Ant.

Note that the DTD generated by this task is incomplete, you can always add XML entities using <taskdef>. See file - the file or single directory of which the permissions + the file or single directory of which the permissions must be changed. exactly one of the two or nested <fileset> elements. dir - the directory which holds the files whose permissions + the directory which holds the files whose permissions must be changed. @@ -1246,7 +1254,7 @@


Cvs

Description

-

Handles packages/modules retrieved from a +

Handles packages/modules retrieved from a CVS repository.

When doing automated builds, the get task should be preferred over the checkout command, because of speed.

@@ -1345,7 +1353,7 @@ includes Comma separated list of patterns of files that must be - deleted. All files are in the current directory + deleted. All files are in the current directory and any sub-directories are deleted when omitted. No @@ -1388,7 +1396,7 @@ includes="**/*.bak" /> -

deletes all files with the extension ".bak" from the current directory +

deletes all files with the extension ".bak" from the current directory and any sub-directories.


Deltree

@@ -1815,7 +1823,7 @@ tablength - The number of characters a TAB stop corresponds to. + The number of characters a TAB stop corresponds to. Must be a positive power of 2, default for this parameter is 8. No @@ -1940,7 +1948,7 @@

Examples

-

<genkey alias="apache-group" storepass="secret" +

<genkey alias="apache-group" storepass="secret" dname="CN=Ant Group, OU=Jakarta Division, O=Apache.org, C=US" />

@@ -1964,10 +1972,10 @@ archive with http/ftp.

The usetimestamps option enables you to control downloads so that the remote file is -only fetched if newer than the local copy. If there is no local copy, the download always takes +only fetched if newer than the local copy. If there is no local copy, the download always takes place. When a file is downloaded, the timestamp of the downloaded file is set to the remote timestamp, -if the JVM is Java1.2 or later. -NB: This timestamp facility only works on downloads using the HTTP protocol. +if the JVM is Java1.2 or later. +NB: This timestamp facility only works on downloads using the HTTP protocol.

Parameters

@@ -2006,13 +2014,13 @@
  <get src="" dest="help/index.html" />

Gets the index page of http://jakarta.apache.org/, and stores it in the file help/index.html.

-
  <get src="" 
-	dest="optional.jar" 
+
  <get src=""
+	dest="optional.jar"
 	verbose="true"
 	usetimestamps="true"/>

Gets the nightly ant build from the tomcat distribution, if the local copy -is missing or out of date. Uses the verbose option +is missing or out of date. Uses the verbose option for progress information.

@@ -2297,9 +2305,9 @@ href="">PATH like structure and can also be set via a nested classpath element.

Example
-
  
+
        <java classname="test.Main" >
-         <arg value="-h" /> 
+         <arg value="-h" />
          <classpath>
            <pathelement location="\test.jar" />
            <pathelement path="${java.class.path}" />
@@ -2310,8 +2318,8 @@
 
  <java classname="test.Main" />
  <java classname="test.Main"
         fork="yes" >
-    <arg value="-h" /> 
-    <jvmarg value="-Xrunhprof:cpu=samples,file=log.txt,depth=3" /> 
+    <arg value="-h" />
+    <jvmarg value="-Xrunhprof:cpu=samples,file=log.txt,depth=3" />
   </java>
 
@@ -2469,7 +2477,7 @@ debug="on" />

compiles all .java files under the directory ${src}, and stores -the .class files in the directory ${build}. +the .class files in the directory ${build}. The classpath used contains xyz.jar, and debug information is on.

  <javac srcdir="${src}"
          destdir="${build}"
@@ -2479,7 +2487,7 @@
          debug="on"
   />

compiles .java files under the directory ${src}, and stores the -.class files in the directory ${build}. +.class files in the directory ${build}. 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 @@ -2520,17 +2528,17 @@ with the obvious restriction that the 1.2 attributes will be ignored if run in a 1.1 VM.

NOTE: since javadoc calls System.exit(), javadoc cannot be run inside the -same VM as ant without breaking functionality. For this reason, this task +same VM as ant without breaking functionality. For this reason, this task always forks the VM. This overhead is not significant since javadoc is normally a heavy application and will be called infrequently.

-

NOTE: the packagelist attribute allows you to specify the list of packages to -document outside of the Ant file. It's a much better practice to include everything -inside the build.xml file. This option was added in order to make it easier to -migrate from regular makefiles, where you would use this option of javadoc. -The packages listed in packagelist are not checked, so the task performs even -if some packages are missing or broken. Use this option if you wish to convert from -an existing makefile. Once things are running you should then switch to the regular -notation. +

NOTE: the packagelist attribute allows you to specify the list of packages to +document outside of the Ant file. It's a much better practice to include everything +inside the build.xml file. This option was added in order to make it easier to +migrate from regular makefiles, where you would use this option of javadoc. +The packages listed in packagelist are not checked, so the task performs even +if some packages are missing or broken. Use this option if you wish to convert from +an existing makefile. Once things are running you should then switch to the regular +notation.

DEPRECATION: the javadoc2 task simply points to the javadoc task and it's there for back compatibility reasons. Since this task will be removed in future @@ -2871,7 +2879,7 @@

- @@ -2882,8 +2890,8 @@
offlineTrue if this link is not available online at the time of + True if this link is not available online at the time of generating the documentation No
Only if the offline attribute is true
- -

groups

+ +

groups

Separates packages on the overview page into whatever groups you specify, one group per table. This performs the same role as the group attribute. You can use either syntax (or both at once), but with the @@ -2930,7 +2938,7 @@ <link offline="true" href="" packagelistLoc="C:\tmp"/> <link href="" </javadoc> - +


Mkdir

Description

@@ -2966,40 +2974,40 @@ Required - patchfile + patchfile the file that includes the diff output Yes - originalfile + originalfile the file to patch - No, tries to guess it from the diff + No, tries to guess it from the diff file - backups + backups Keep backups of the unpatched files No - quiet + quiet Work silently unless an error occurs No - reverse - Assume patch was created with old and new files + reverse + Assume patch was created with old and new files swapped. No - ignorewhitespace + ignorewhitespace Ignore whitespace differences. No - strip - Strip the smallest prefix containing num leading + strip + Strip the smallest prefix containing num leading slashes from filenames. No @@ -3014,7 +3022,7 @@
 --- a/mod1.0/A	Mon Jun  5 17:28:41 2000
 +++ a/mod1.1/A	Mon Jun  5 17:28:49 2000
-
+ the leading a/ will be stripped.

Property

@@ -3079,7 +3087,7 @@ builds using the following:
  <property file="${user.home}/.ant-global.properties" />

since the "user.home" property is defined by the Java virtual machine -to be your home directory. This technique is more appropriate for Unix than +to be your home directory. This technique is more appropriate for Unix than Windows since the notion of a home directory doesn't exist on Windows. On the JVM that I tested, the home directory on Windows is "C:\". Different JVM implementations may use other values for the home directory on Windows. @@ -3111,14 +3119,14 @@

Examples

-
  <rename src="" dest="${name}-${version}.jar" />
+
  <rename src="" dest="${name}-${version}.jar" />

Renames the file foo.jar to ${name}-${version}.jar (assuming name and version being predefined properties). If a file named ${name}-${version}.jar already exists, it will be removed prior to renaming foo.jar.


Replace

Description

-

Replace is a directory based task for replacing the occurrence of a given string with another string +

Replace is a directory based task for replacing the occurrence of a given string with another string in selected file.

If you want to replace a text that crosses line boundaries, you must use a nested <replacetoken> element.

@@ -3136,7 +3144,7 @@ dir - The base directory to use when replacing a token in + The base directory to use when replacing a token in multiple files. @@ -3195,7 +3203,7 @@ cross line boundaries, you can use nested elements to specify them.

Examples

-
  
+
 <replace dir="${src}" value="wombat">
   <include name="**/*.html" />
   <replacetoken><[CDATA[multi line
@@ -3206,7 +3214,7 @@
 line\ntoken" with the string "wombat", in all
 HTML files in the directory ${src}.Where \n is
 the platform specific line separator.

-
  
+
 <replace file="${src}/index.html">
   <replacetoken><[CDATA[two line
 token]]></replacetoken>
@@ -3312,7 +3320,7 @@
   
   
     verify
-    check that classes implement Remote before handing them 
+    check that classes implement Remote before handing them
         to rmic (default is false)
     No
   
@@ -3682,7 +3690,7 @@
 

Unjar/Unzip

Description

Unzips a zip- or jarfile.

-

For JDK 1.1 "last modified time" field is set to current time instead of being +

For JDK 1.1 "last modified time" field is set to current time instead of being carried from zipfile.

File permissions will not be restored on extracted files.

Parameters

@@ -3713,7 +3721,7 @@

Description

Untars a tarfile.

File permissions will not be restored on extracted files. -

For JDK 1.1 "last modified time" field is set to current time instead of being +

For JDK 1.1 "last modified time" field is set to current time instead of being carried from tarfile.

Parameters

@@ -3754,7 +3762,7 @@ 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. +inclusion/exclusion of files works, and how to write patterns.

This task forms an implicit FileSet and supports all attributes of <fileset> (dir becomes basedir) as well as the nested @@ -3958,7 +3966,7 @@

Examples

 <cab cabfile="${dist}/manual.cab"
-     basedir="htdocs/manual" 
+     basedir="htdocs/manual"
   />
 

cabs all files in the htdocs/manual directory in a file called @@ -4030,33 +4038,33 @@

- - - - - @@ -4087,8 +4095,8 @@ <fileset dir="htdocs/manual" /> </ftp> -

Logs in to ftp.apache.org as anonymous and -uploads all files in the htdocs/manual directory +

Logs in to ftp.apache.org as anonymous and +uploads all files in the htdocs/manual directory to the default directory for that user.

  <ftp server="ftp.apache.org"
        remotedir="incoming"
@@ -4098,8 +4106,8 @@
   >
     <fileset dir="htdocs/manual" />
   </ftp>
-

Logs in to ftp.apache.org as anonymous and -uploads all new or changed files in the htdocs/manual directory +

Logs in to ftp.apache.org as anonymous and +uploads all new or changed files in the htdocs/manual directory to the incoming directory relative to the default directory for anonymous.

  <ftp server="ftp.apache.org"
@@ -4114,9 +4122,9 @@
       <include name="**/*.html" />
     </fileset>
   </ftp>
-

Logs in to ftp.apache.org at port 2121 as -coder with password java1 and uploads all new or -changed HTML files in the htdocs/manual directory to the +

Logs in to ftp.apache.org at port 2121 as +coder with password java1 and uploads all new or +changed HTML files in the htdocs/manual directory to the /pub/incoming directory. The files are transferred in text mode.

  <ftp server="ftp.nt.org"
@@ -4130,13 +4138,13 @@
       <include name="**/*.html" />
     </fileset>
   </ftp>
-

Logs in to the Windows-based ftp.nt.org as -coder with password java1 and uploads all -HTML files in the htdocs/manual directory to the +

Logs in to the Windows-based ftp.nt.org as +coder with password java1 and uploads all +HTML files in the htdocs/manual directory to the c:\uploads directory. Progress messages are displayed as each file is uploaded.

Getting Files

-

Getting files from an FTP server works pretty much the same way as +

Getting files from an FTP server works pretty much the same way as sending them does. The only difference is that the nested filesets use the remotedir attribute as the base directory for the files on the FTP server, and the dir attribute as the local directory to put the files @@ -4151,12 +4159,12 @@ </fileset> </ftp> -

Logs in to ftp.apache.org as anonymous and -recursively downloads all .html files from default directory for that user +

Logs in to ftp.apache.org as anonymous and +recursively downloads all .html files from default directory for that user into the htdocs/manual directory on the local machine.

Deleting Files

-As you've probably guessed by now, you use nested fileset elements to -select the files to delete from the remote FTP server. Again, the +As you've probably guessed by now, you use nested fileset elements to +select the files to delete from the remote FTP server. Again, the filesets are relative to the remote directory, not a local directory. In fact, the dir attribute of the fileset is ignored completely.
@@ -4177,7 +4185,7 @@
   <ftp action=""
        server="ftp.apache.org"
        userid=quot;anonymous"
-       password="[EMAIL PROTECTED]" 
+       password="[EMAIL PROTECTED]"
        listing="data/ftp.listing" >
     <fileset>
       <include name="**" />
@@ -4196,17 +4204,17 @@
 NetRexx source files to compile.  Only NetRexx files that have no corresponding
 class file or where the class file is older than the java file will be compiled.

Files in the source tree are copied to the destination directory, -allowing support files to be located properly in the classpath. The source +allowing support files to be located properly in the classpath. The source files are copied because the NetRexx compiler cannot produce class files in a specific directory via parameters

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 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 @@ -4372,8 +4380,8 @@

@@ -4391,8 +4399,8 @@ - @@ -4453,13 +4461,13 @@

RenameExtensions

Description:

Renames files in the srcDir directory ending with the -fromExtension string so that they end with the -toExtension string. Files are only replaced if +fromExtension string so that they end with the +toExtension string. Files are only replaced if replace is true

-

See the section on +

See the section on directory based tasks, on how the -inclusion/exclusion of files works, and how to write patterns. +inclusion/exclusion of files works, and how to write patterns. This task forms an implicit FileSet and supports all attributes of <fileset> (dir becomes srcDir) as well as the nested @@ -4542,7 +4550,7 @@


Script

Description:

-

Execute a script in a +

Execute a script in a BSF supported language.

All items (tasks, targets, etc) of the running project are accessible from the script, using either their name or @@ -4711,13 +4719,13 @@


Build Events

-Ant is capable of generating build events as it performs the tasks necessary to build a project. +Ant is capable of generating build events as it performs the tasks necessary to build a project. Listeners can be attached to ant to receive these events. This capability could be used, for example, -to connect Ant to a GUI or to integrate Ant with an IDE. +to connect Ant to a GUI or to integrate Ant with an IDE. -

To use build events you need to create an ant Project object. You can then call the +

To use build events you need to create an ant Project object. You can then call the addBuildListener method to add your listener to the project. Your listener must implement -the org.apache.tools.antBuildListener interface. The listener will receive BuildEvents +the org.apache.tools.antBuildListener interface. The listener will receive BuildEvents for the following events

  • Build started @@ -4733,7 +4741,7 @@
    ant -listener org.apache.tools.ant.XmlLogger
    -will run ant with a listener which generates an XML representation of the build progress. This +will run ant with a listener which generates an XML representation of the build progress. This listener is included with ant as is the default listener which generates the logging to standard output. @@ -4743,27 +4751,27 @@

    It is very easy to write your own task:

    1. Create a Java class that extends org.apache.tools.ant.Task.
    2. -
    3. For each attribute, write a setter method. The setter method must be a +
    4. For each attribute, write a setter method. The setter method must be a public void method that takes a single argument. The name of the method must begin with "set", followed by the attribute name, with the first character in uppercase, and the rest in - lowercase. The type of the attribute can be String, any - primitive type, Class, File (in which case the - value of the attribute is interpreted relative to the project's basedir) + lowercase. The type of the attribute can be String, any + primitive type, Class, File (in which case the + value of the attribute is interpreted relative to the project's basedir) or any other type that has a constructor with a single String argument
    5. If your task has enumerated attributes, you should consider using a subclass of org.apache.tools.ant.types.EnumeratedAttribute as argument to your setter method. See org.apache.tools.ant.taskdefs.FixCRLF for an example.
    6. -
    7. If the task should support character data, write a public void +
    8. If the task should support character data, write a public void addText(String) method.
    9. -
    10. For each nested element, write a create or add method. A create method - must be a public method that takes no arguments and returns - an Object type. The name of the create method must begin with - "create", followed by the element name. An add method must be - a public void method that takes a single argument of an - Object type with a no argument constructor. The name of the add method +
    11. For each nested element, write a create or add method. A create method + must be a public method that takes no arguments and returns + an Object type. The name of the create method must begin with + "create", followed by the element name. An add method must be + a public void method that takes a single argument of an + Object type with a no argument constructor. The name of the add method must begin with "add", followed by the element name.
    12. Write a public void execute method, with no arguments, that throws a BuildException. This method implements the task
      --- bbuild.xml	Sat Sep 09 08:36:50 2000
      +++ build.xml	Mon Sep 11 09:45:14 2000
      @@ -6,7 +6,7 @@
       
       <project name="Ant" default="main" basedir=".">
       
      -  <!-- Give user a chance to override without editing this file 
      +  <!-- Give user a chance to override without editing this file
              (and without typing -D each time it compiles it -->
         <property file="${user.home}/.ant.properties" />
       
      @@ -52,9 +52,9 @@
           <available property="jdk1.3+" classname="java.lang.StrictMath" />
           <available property="bsf.present" classname="com.ibm.bsf.BSFManager" />
           <available property="netrexx.present" classname="netrexx.lang.Rexx" />
      -    <available property="xslp.present" 
      +    <available property="xslp.present"
                      classname="com.kvisco.xsl.XSLProcessor" />
      -    <available property="xalan.present" 
      +    <available property="xalan.present"
                      classname="org.apache.xalan.xslt.XSLTProcessorFactory" />
           <available property="ejb.ejbc.present" classname="weblogic.ejbc" />
           <available property="ejb.DDCreator.present" classname="weblogic.ejb.utils.DDCreator" />
      @@ -99,7 +99,7 @@
             <exclude name="**/FTP*.java" unless="ftp.present" />
             <exclude name="**/AntStarTeam*.java" unless="starteam.present" />
           </javac>
      - 
      +
           <copydir src="${src.dir}" dest="${build.classes}">
             <include name="**/*.properties" />
           </copydir>
      @@ -107,8 +107,8 @@
           <filter token="VERSION" value="${version}" />
           <filter token="DATE" value="${TODAY}" />
           <filter token="TIME" value="${TSTAMP}" />
      -    <copydir src="${src.dir}" 
      -             dest="${build.classes}" 
      +    <copydir src="${src.dir}"
      +             dest="${build.classes}"
                    forceoverwrite="true"
                    filtering="on">
             <include name="**/version.txt" />
      @@ -131,7 +131,7 @@
         <!-- =================================================================== -->
         <!-- Creates the binary structure                                        -->
         <!-- =================================================================== -->
      -  <target name="main" depends="jar">
      +  <target name="main" depends="jar" description="Creates the binary structure">
            <mkdir dir="${bin.dir}"/>
            <copydir src="${src.bin.dir}" dest="${bin.dir}"/>
            <chmod perm="+x">
      @@ -146,7 +146,7 @@
         <!-- =================================================================== -->
         <!-- Creates the API documentation                                       -->
         <!-- =================================================================== -->
      -  <target name="javadocs" depends="prepare">
      +  <target name="javadocs" depends="prepare" description="Creates the API documentation">
           <mkdir dir="${build.javadocs}"/>
           <javadoc packagenames="${packages}"
                    sourcepath="${basedir}/${src.dir}"
      @@ -162,7 +162,7 @@
         <!-- =================================================================== -->
         <!-- Creates the distribution                                            -->
         <!-- =================================================================== -->
      -  <target name="dist" depends="main,jar,javadocs">
      +  <target name="dist" depends="main,jar,javadocs" description="Creates the distribution">
            <mkdir dir="${ant.dist.dir}"/>
            <mkdir dir="${ant.dist.dir}/bin"/>
            <mkdir dir="${ant.dist.dir}/lib"/>
      @@ -207,11 +207,11 @@
         <!-- =================================================================== -->
         <!-- Installs the ant.jar library and binary files into ant.home         -->
         <!-- =================================================================== -->
      -  <target name="bootstrap" depends="main">
      +  <target name="bootstrap" depends="main" description="Installs the ant.jar library and binary files into ant.home">
           <echo message="copying bootstrapped files into bin and lib"/>
           <copydir src="${lib.dir}" dest="lib"/>
           <copydir src="${bin.dir}" dest="bin"/>
      -  </target>     
      +  </target>
       
         <target name="install" depends="dist" if="ant.install">
           <echo message="installing full copy of ant into ${ant.install}"/>
      @@ -222,10 +222,10 @@
               <patternset refid="chmod.patterns"/>
             </fileset>
           </chmod>
      -  </target>     
      +  </target>
       
         <target name="fullinstall" depends="install"/>
      -  
      +
         <target name="mininstall" depends="main" if="ant.install">
           <echo message="copy minimal ant installation into ${ant.install}"/>
           <mkdir dir="${ant.install}"/>
      @@ -236,7 +236,7 @@
               <patternset refid="chmod.patterns"/>
             </fileset>
           </chmod>
      -  </target>     
      +  </target>
       
         <!-- =================================================================== -->
         <!-- Cleans up generated stuff                                           -->
      
      --- bbuildAnt.xml	Thu Apr 27 20:26:10 2000
      +++ buildAnt.xml	Mon Sep 11 09:41:49 2000
      @@ -69,7 +69,7 @@
       
         <!-- Install the distributable files to the Jakarta server -->
         <!-- Obviously, this will only work right on the real server!!! -->
      -  <target name="install">
      +  <target name="install" description="Install the distributable files to the Jakarta server">
           <copydir src="${buildAnt.uploads}" dest="${buildAnt.server}"
                    includes="${buildAnt.name}-${DSTAMP}.*"/>
           <chmod   src="${buildAnt.server}/${buildAnt.name}-${DSTAMP}.*"
      @@ -79,6 +79,6 @@
         </target>
       
         <!-- All-in-one target (except for install) -->
      -  <target name="all" depends="extract,build,addons,package"/>
      +  <target name="all" depends="extract,build,addons,package" description="All-in-one target (except for install)"/>
       
       </project>
      

      Attachment: patch-main.java
      Description: Binary data

      Reply via email to

remotedirthe directory to which to upload files on the + the directory to which to upload files on the ftp server. No
actionthe ftp action to perform, defaulting to "send". + the ftp action to perform, defaulting to "send". Currently supports"put", "get", "del", and "list". No
binaryselects binary-mode ("yes") or text-mode - ("no") transfers. + selects binary-mode ("yes") or text-mode + ("no") transfers. Defaults to "yes" No
verbosedisplays information on each file transferred if set + displays information on each file transferred if set to "yes". Defaults to "no". No
dependstransfers only new or changed files if set to + transfers only new or changed files if set to "yes". Defaults to "no". No
strictargs Tells the NetRexx compiler that method calls always - need parentheses, even if no arguments are needed, e.g. - aStringVar.getBytes vs. + need parentheses, even if no arguments are needed, e.g. + aStringVar.getBytes vs. aStringVar.getBytes() No
strictimportWhether classes need to be imported explicitly using an - import statement. By default the NetRexx compiler will + Whether classes need to be imported explicitly using an + import statement. By default the NetRexx compiler will import certain packages automatically No