| vmlauncher |
Run command using the JVM's execution facilities where available. If set to false the
- underlying OS's shell, either directly or through the antRun scripts, will be
+ underlying OS's shell, either directly or through the antRun scripts, will be
used. Under some operating systems, this gives access to facilities not normally available
through JVM including, under Windows, being able to execute scripts, rather than their
associated interpreter. If you want to specify the name of the executable as a relative path
@@ -360,9 +360,9 @@ of exec.
</fileset>
<fileset refid="other.files"/>
</apply>
-invokes ls -l, adding the absolute filenames of all files below /tmp
-not ending in .txt and all files of the FileSet
-with id other.files to the command line.
+invokes ls -l, adding the absolute filenames of all files below /tmp not
+ending in .txt and all files of the FileSet with id other.files
+to the command line.
<apply executable="somecommand" parallel="false">
<arg value="arg1"/>
@@ -384,7 +384,7 @@ with the absolute filenames of all files separated by spaces.
<fileset dir="src/C" includes="*.c"/>
<mapper type="glob" from="*.c" to="*.o"/>
</apply>
-invokes cc -c -o TARGETFILE SOURCEFILE for each .c file that is newer
+ invokes cc -c -o TARGETFILE SOURCEFILE for each .c file that is newer
than the corresponding .o, replacing TARGETFILE with the absolute filename
of the .o and SOURCEFILE with the absolute name of the .c
file.
@@ -400,7 +400,7 @@ file.
<outputmapper refid="out"/>
</redirector>
</apply>
-Applies the fictitious processfile executable to all files
+ Applies the fictitious processfile executable to all files
matching *.file in the src directory.
The out <mapper> has been set up to map *.file
to *.out, then this <mapper> is used to
@@ -416,7 +416,7 @@ dependency checking against output files—the target files in this case.
-Applies the ls executable to all directories in the PATH, effectively
+ Applies the ls executable to all directories in the PATH, effectively
listing all executables that are available on the PATH.
@@ -431,7 +431,7 @@ listing all executables that are available on the PATH.
<outputmapper id="out" type="glob" from="*.js" to="dest/*.js"/>
</redirector>
</apply>
-Conversion of the command jsmin < src/a.js > dest/a.js but for all files in
+ Conversion of the command jsmin < src/a.js > dest/a.js but for all files in
the src directory. Because the filename itself should not be passed to
the jsmin program, the addsourcefile is set to false .
diff --git a/manual/Tasks/attrib.html b/manual/Tasks/attrib.html
index 1051644fe..07e59897a 100644
--- a/manual/Tasks/attrib.html
+++ b/manual/Tasks/attrib.html
@@ -104,7 +104,7 @@ alternative.
+<!-- Convert path to URL format -->
<pathconvert dirsep="/" property="xsd.file">
<path>
<pathelement location="xml/doc.xsd"/>
diff --git a/manual/Tasks/zip.html b/manual/Tasks/zip.html
index 28fc209e2..c83a28c90 100644
--- a/manual/Tasks/zip.html
+++ b/manual/Tasks/zip.html
@@ -82,8 +82,8 @@ see below
(see description of the filemode and dirmode attributes
for <zipfileset>). Unfortunately there is no portable
way to store these permissions. Ant uses the algorithm used by Info-Zip's implementation of the zip and unzip
-commands—these are the default versions of zip and unzip for many
+target="_top">Info-Zip's implementation of the zip and unzip
+commands—these are the default versions of zip and unzip for many
Unix(-like) systems.
Please note that the zip format allows multiple files of the same fully-qualified name to
@@ -264,8 +264,8 @@ extract an Ant generated ZIP archive.
sufficient for many international character sets.
Over time different archivers have chosen different ways to work around the
-limitation—the java.util.zip packages simply uses UTF-8 as its encoding for
-example.
+limitation—the java.util.zip packages simply uses UTF-8 as its
+encoding for example.
Ant has been offering the encoding attribute of the zip
and unzip task as a way to explicitly specify the encoding to use (or expect) since
@@ -307,13 +307,13 @@ ZIP archives. Below are some test results which may be superseded with later ve
tool.
- - The
java.util.zip package used by the jar executable or to read jars
- from your CLASSPATH reads and writes UTF-8 names, it doesn't set or recognize any
- flags or unicode extra fields.
- - Since Java 7,
java.util.zip writes UTF-8 by default and uses the language
- encoding flag. It is possible to specify a different encoding when reading/writing ZIPs via new
- constructors. The package now recognizes the language encoding flag when reading and ignores
- the Unicode extra fields.
+ - The
java.util.zip package used by the jar executable or
+ to read jars from your CLASSPATH reads and writes UTF-8 names, it doesn't set or
+ recognize any flags or unicode extra fields.
+ - Since Java 7,
java.util.zip writes UTF-8 by default and uses the
+ language encoding flag. It is possible to specify a different encoding when reading/writing
+ ZIPs via new constructors. The package now recognizes the language encoding flag when reading
+ and ignores the Unicode extra fields.
- 7Zip writes CodePage 437 by default but uses UTF-8 and the language encoding flag when writing
entries that cannot be encoded as CodePage 437 (similar to the
zip task
with fallbacktoUTF8 set to true ). It recognizes the language encoding flag
@@ -332,16 +332,16 @@ tool.
So, what to do?
-If you are creating jars, then java.util.zip is your main consumer. We recommend
-you set the encoding to UTF-8 and keep the language encoding flag enabled. The flag won't help or
-hurt java.util.zip prior to Java 7 but archivers that support it will show the correct
-file names.
+If you are creating jars, then java.util.zip is your main consumer. We
+recommend you set the encoding to UTF-8 and keep the language encoding flag enabled. The flag won't
+help or hurt java.util.zip prior to Java 7 but archivers that support it
+will show the correct file names.
For maximum interoparability it is probably best to set the encoding to UTF-8, enable the
language encoding flag and create Unicode extra fields when writing ZIPs. Such archives should be
-extracted correctly by java.util.zip, 7Zip, WinZIP, PKWARE tools and most likely
-InfoZIP tools. They will be unusable with Windows' "compressed folders" feature and bigger than
-archives without the Unicode extra fields, though.
+extracted correctly by java.util.zip, 7Zip, WinZIP, PKWARE tools and most
+likely InfoZIP tools. They will be unusable with Windows' "compressed folders" feature and bigger
+than archives without the Unicode extra fields, though.
If Windows' "compressed folders" is your primary consumer, then your best option is to explicitly
set the encoding to the target platform. You may want to enable creation of Unicode extra fields so
@@ -376,9 +376,9 @@ the zip family of tasks. It supports three values:
limits of traditional zip files but don't want to waste too much space (the Zip64 extensions take up
extra space). Unfortunately some ZIP implementations don't understand Zip64 extra fields or fail to
parse archives with extra fields in local file headers that are not present in the central
-directory, one such implementation is the java.util.zip package of Java 5, that's why
-the jar tasks default to never . Archives created with as-needed can be
-read without problems with Java 6 and later.
+directory, one such implementation is the java.util.zip package of Java 5,
+that's why the jar tasks default to never . Archives created
+with as-needed can be read without problems with Java 6 and later.
Parameters specified as nested elements
diff --git a/manual/Types/antlib.html b/manual/Types/antlib.html
index bafc2f9ad..515e39ff4 100644
--- a/manual/Types/antlib.html
+++ b/manual/Types/antlib.html
@@ -27,10 +27,10 @@
Description
- An antlib file is an xml file with a root element of antlib. Antlib's
- elements are Apache Ant definition
- tasks—like Taskdef or any Ant task that
- extends org.apache.tools.ant.taskdefs.AntlibDefinition.
+ An antlib file is an xml file with a root element of antlib. Antlib's elements
+ are Apache Ant definition tasks—like Taskdef or any
+ Ant task that
+ extends org.apache.tools.ant.taskdefs.AntlibDefinition.
The current set of declarations bundled with Ant that do this are:
diff --git a/manual/Types/classfileset.html b/manual/Types/classfileset.html
index f394b2dcc..eaf4a1608 100644
--- a/manual/Types/classfileset.html
+++ b/manual/Types/classfileset.html
@@ -77,11 +77,11 @@ may be used
RootFileSet
-A root fileset is used to add a set of root classes from a fileset. In this case the entries in
-the fileset are expected to be Java class files. The name of the Java class is determined by the
+A root fileset is used to add a set of root classes from a fileset. In this case the entries in the
+fileset are expected to be Java class files. The name of the Java class is determined by the
relative location of the classfile in the fileset. So, the
file org/apache/tools/ant/Project.class corresponds to the Java
-class org.apache.tools.ant.Project.
+class org.apache.tools.ant.Project.
Examples
@@ -90,8 +90,8 @@ class org.apache.tools.ant.Project.
</classfileset>
This example creates a fileset containing all the class files upon which
-the org.apache.tools.ant.Project class depends. This fileset could then be used to
-create a jar.
+the org.apache.tools.ant.Project class depends. This fileset could then be
+used to create a jar.
@@ -104,8 +104,9 @@ create a jar.
<rootfileset dir="${classes.dir}" includes="org/apache/tools/ant/Project*.class"/>
</classfileset>
-This example constructs the classfileset using all the class with names starting with Project in
-the org.apache.tools.ant package.
+This example constructs the classfileset using all the class with names starting
+with Project in the org.apache.tools.ant
+package.
|