-Ant lets you call JUnit +Ant lets you call JUnit tasks, which unit test the code your team has written. Automated testing may seem like extra work at first, but JUnit makes writing unit tests so easy that you have almost no reason not to. Invest the time in learning @@ -203,7 +203,7 @@ given the choice.
System tests are harder to automate than unit tests, but if you can write java code to stress large portions of the system - even if the code -can not run as JUnit tasks - then the java +can not run as JUnit tasks - then the java task can be used to invoke them. It is best to specify that you want a new JVM for these tests, so that a significant crash does not break the full build. The Junit extensions such as @@ -263,8 +263,8 @@ The common barriers to cross-platform Ant are the use of command line tools (exec tasks) which are not portable, path issues, and hard coding in the location of things. -
There is also the PathConvert task which +href="manual/Tasks/pathconvert.html">PathConvert task which can put a fully resolved path into a property. Why do that? Because then you can use that path in other ways - such as pass it as a parameter to some application you are calling, or use the replace task to patch it @@ -326,14 +326,14 @@ find any .java files. The Java compiler is of course case sensitive - y not have a class 'ExampleThree' implemented in "examplethree.java".
-Some tasks only work on one platform -
+Some tasks only work on one platform -
Chmod being a classic example. These tasks usually result in just a
warning message on an unsupported platform - the rest of the target's
tasks will still be called. Other tasks degrade their functionality on
platforms or Java versions. In particular, any task which adjusts the
timestamp of files can not do so properly on Java 1.1. Tasks which can
-do that - Get, Touch and
+do that - Get, Touch and
Unjar/Unwar/Unzip for example, degrade their functionality on
Java1.1, usually resorting to the current timestamp instead.
@@ -348,7 +348,7 @@ on Windows, OS/2 and Unix and hence called from Ant without issues. The
perl code can be left to resolve its own platform issues. Don't forget to
set the line endings of the file to the appropriate platform when you
redistribute Perl code; fixCRLF
+href="manual/Tasks/fixcrlf.html">fixCRLF
can do that for you.
@@ -381,36 +381,36 @@ processes for deploying Java to remote sites are reasonably well
evolved in Ant. That is because we all have to do it these days, so
many people have put in the effort to make the tasks easier.
-Ant can Jar, Tar or Zip files for deployment, while the
-War task extends the jar task
+Ant can Jar, Tar or Zip files for deployment, while the
+War task extends the jar task
for better servlet deployment.
-Jlink is a
+Jlink is a
jar generation file which lets you merge multiple sub jars. This is
ideal for a build process in which separate jars are generated by sub
projects, yet the final output is a merged jar. Cab can be used on Win32 boxes to
+"manual/Tasks/cab.html">Cab
The ftp task lets you move stuff up to a server. Beware of putting the ftp password in the build file - a property file with tight access control is slightly better. The FixCRLF task is often a useful interim step if +"manual/Tasks/fixcrlf.html">FixCRLF task is often a useful interim step if you need to to adjust the line endings of files. A WebDav task has long been discussed, which would provide a more secure upload to web servers, but it is still in the todo list. Rumour has it that there is such a task in the jakarta-slide libraries. With MacOS X, Linux and Windows XP all supporting WebDAV file systems, you may even be able -to use copy to deploy +to use copy to deploy though a firewall.
-EJB deployment is aided by the ejb tasks, +EJB deployment is aided by the ejb tasks, while the serverdeploy +href="manual/Tasks/serverdeploy.html">serverdeploy suite can deploy to multiple servers. The popularity of Ant has encouraged vendors to produce their own deployment tasks which they redistribute with their servers. For example, the Tomcat4.1 installation @@ -418,9 +418,9 @@ includes tasks to deploy, undeploy and reload web applications.
Finally, there are of course the fallbacks of just copying files to a -destination using Copy and Copydir , or just sending them to a person or -process using Mail or the attachment -aware MimeMail. +destination using Copy and Copydir , or just sending them to a person or +process using Mail or the attachment +aware MimeMail. In one project our team even used Ant to build CD images through a build followed by a long set of Copy tasks, which worked surprisingly well, certainly easier than when we mailed them to the free email service on @@ -673,7 +673,7 @@ Tips and Tricks get
The <import> task does powerful things, such as let you override targets, and use ant properties to name the location of the file to import. Consult the -documentation for the specifics of +documentation for the specifics of these features.
@@ -791,7 +791,7 @@ Implement complex Ant builds through XSL
You can specify a set of properties to be copied into the new project with propertysets.
+href="../Types/propertyset.html">propertysets.since Ant 1.6.
diff --git a/docs/manual/CoreTasks/antcall.html b/docs/manual/Tasks/antcall.html similarity index 99% rename from docs/manual/CoreTasks/antcall.html rename to docs/manual/Tasks/antcall.html index 32ee0b599..52321c11c 100644 --- a/docs/manual/CoreTasks/antcall.html +++ b/docs/manual/Tasks/antcall.html @@ -148,7 +148,7 @@ optionally changing their id.You can specify a set of properties to be copied into the new project with propertysets.
+href="../Types/propertyset.html">propertysets.since Ant 1.6.
diff --git a/docs/manual/OptionalTasks/antlr.html b/docs/manual/Tasks/antlr.html similarity index 100% rename from docs/manual/OptionalTasks/antlr.html rename to docs/manual/Tasks/antlr.html diff --git a/docs/manual/CoreTasks/antstructure.html b/docs/manual/Tasks/antstructure.html similarity index 97% rename from docs/manual/CoreTasks/antstructure.html rename to docs/manual/Tasks/antstructure.html index 252cb24f9..5fb09785a 100644 --- a/docs/manual/CoreTasks/antstructure.html +++ b/docs/manual/Tasks/antstructure.html @@ -35,7 +35,7 @@ usage of XML cannot be captured with a DTD. Several elements in Ant can have different attribute lists depending on the element that contains them. "fail" for example can be the task or the nested child element of the sound task. Don't consider the +href="../Tasks/sound.html">sound task. Don't consider the generated DTD something to rely upon.Also note that the DTD generated by this task is incomplete, you can diff --git a/docs/manual/CoreTasks/antversion.html b/docs/manual/Tasks/antversion.html similarity index 100% rename from docs/manual/CoreTasks/antversion.html rename to docs/manual/Tasks/antversion.html diff --git a/docs/manual/CoreTasks/apply.html b/docs/manual/Tasks/apply.html similarity index 97% rename from docs/manual/CoreTasks/apply.html rename to docs/manual/Tasks/apply.html index f5ee80ff9..b6df73260 100644 --- a/docs/manual/CoreTasks/apply.html +++ b/docs/manual/Tasks/apply.html @@ -33,16 +33,16 @@ the command is only executed when Ant is run on one of the specified operating systems.
The files and/or directories of a number of Resource Collections +href="../Types/resources.html#collection">Resource Collections – including but not restricted to - FileSets, - DirSets + FileSets, + DirSets (since Ant 1.6) or - FileLists + FileLists (since Ant 1.6) – are passed as arguments to the system command.
-If you specify a nested mapper, +
If you specify a nested mapper, the timestamp of each source file is compared to the timestamp of a target file which is defined by the nested mapper element and searched for in the given dest, if specified.
@@ -312,7 +312,7 @@ elements to define the files for this task and refer to elements to define the directories for this task and refer to<dirset>s defined elsewhere.
-since Ant 1.7
You can use any number of nested resource collections.
@@ -383,7 +383,7 @@ system command via nested<env> elements. See the
description in the section about exec
A nested I/O Redirector +
A nested I/O Redirector can be specified. <apply>'s behavior is like that of exec with regard to redirectors, with the exception that, in non-parallel mode, diff --git a/docs/manual/CoreTasks/apt.html b/docs/manual/Tasks/apt.html similarity index 100% rename from docs/manual/CoreTasks/apt.html rename to docs/manual/Tasks/apt.html diff --git a/docs/manual/OptionalTasks/attrib.html b/docs/manual/Tasks/attrib.html similarity index 94% rename from docs/manual/OptionalTasks/attrib.html rename to docs/manual/Tasks/attrib.html index 1b72aac1b..8215710f2 100644 --- a/docs/manual/OptionalTasks/attrib.html +++ b/docs/manual/Tasks/attrib.html @@ -33,14 +33,14 @@ directories. Right now it has effect only under Windows. Each of the 4 possible permissions has its own attribute, matching the arguments for the attrib command.
-FileSets, -DirSets or FileLists can be specified using +
FileSets,
+DirSets or FileLists can be specified using
nested <fileset>, <dirset> and
<filelist> elements.
Starting with Ant 1.7, this task supports arbitrary Resource Collections +href="../Types/resources.html#collection">Resource Collections as nested elements.
By default this task will use a single invocation of the underlying @@ -126,7 +126,7 @@ directory tree), so you'll have to experiment a little.
build.number to the value that was read in
(or to 0, if no such value). It will then increment the
number by one and write it back out to the file.
(See the
-PropertyFile task
+PropertyFile task
if you need finer control over things such as the property name or
the number format.)
diff --git a/docs/manual/OptionalTasks/cab.html b/docs/manual/Tasks/cab.html
similarity index 95%
rename from docs/manual/OptionalTasks/cab.html
rename to docs/manual/Tasks/cab.html
index cd7504d82..e981827a5 100644
--- a/docs/manual/OptionalTasks/cab.html
+++ b/docs/manual/Tasks/cab.html
@@ -27,7 +27,7 @@
The cab task creates Microsoft cab archive files. It is invoked -similar to the jar or zip tasks. +similar to the jar or zip tasks. This task will work on Windows using the external cabarc tool (provided by Microsoft) which must be located in your executable path.
To use this task on other platforms you need to download and compile libcabinet from @@ -36,7 +36,7 @@ http://trill.cis.fordham.edu/~barbacha/cabinet_library/.
See the section on directory based tasks, on how the inclusion/exclusion of files works, and how to write patterns.
-This task forms an implicit FileSet and +
This task forms an implicit FileSet and
supports most attributes of <fileset>
(dir becomes basedir) as well as the nested
<include>, <exclude> and
@@ -112,7 +112,7 @@ supports most attributes of <fileset>
The cab task supports one nested <fileset>
+href="../Types/fileset.html"><fileset>
element to specify the files to be included in the archive.
If this is specified, the "basedir" attribute cannot be used.
- Resource collections are + Resource collections are used to select files for which checksums should be generated.
diff --git a/docs/manual/OptionalTasks/chgrp.html b/docs/manual/Tasks/chgrp.html similarity index 95% rename from docs/manual/OptionalTasks/chgrp.html rename to docs/manual/Tasks/chgrp.html index 6c2993c2c..9d676f8c0 100644 --- a/docs/manual/OptionalTasks/chgrp.html +++ b/docs/manual/Tasks/chgrp.html @@ -33,14 +33,14 @@ directories. Right now it has effect only under Unix. The group attribute is equivalent to the corresponding argument for the chgrp command. -FileSets, -DirSets or FileLists can be specified using +
FileSets,
+DirSets or FileLists can be specified using
nested <fileset>, <dirset> and
<filelist> elements.
Starting with Ant 1.7, this task supports arbitrary Resource Collections +href="../Types/resources.html#collection">Resource Collections as nested elements.
By default this task will use a single invocation of the underlying @@ -120,7 +120,7 @@ could use as initial value for these experiments.
This task holds an implicit FileSet and supports all of
+href="../Types/fileset.html">FileSet and supports all of
FileSet's attributes and nested elements directly. More sets can be
specified using nested <fileset> or
<dirset> (since Ant 1.6) elements.
Starting with Ant 1.6, this task also supports nested filelists.
+href="../Types/filelist.html">filelists.Starting with Ant 1.7, this task supports arbitrary Resource Collections +href="../Types/resources.html#collection">Resource Collections as nested elements.
By default this task will use a single invocation of the underlying diff --git a/docs/manual/OptionalTasks/chown.html b/docs/manual/Tasks/chown.html similarity index 95% rename from docs/manual/OptionalTasks/chown.html rename to docs/manual/Tasks/chown.html index 4714fa442..d44035c1c 100644 --- a/docs/manual/OptionalTasks/chown.html +++ b/docs/manual/Tasks/chown.html @@ -33,14 +33,14 @@ directories. Right now it has effect only under Unix. The owner attribute is equivalent to the corresponding argument for the chown command.
-FileSets, -DirSets or FileLists can be specified using +
FileSets,
+DirSets or FileLists can be specified using
nested <fileset>, <dirset> and
<filelist> elements.
Starting with Ant 1.7, this task supports arbitrary Resource Collections +href="../Types/resources.html#collection">Resource Collections as nested elements.
By default this task will use a single invocation of the underlying @@ -119,7 +119,7 @@ could use as initial value for these experiments.
defines two components with the same name "or"; one is a condition (see conditions) and one is - a selector (see selectors). + a selector (see selectors).