From 786e2e2e1cf34805da69f13fa1d7dd06da1a1454 Mon Sep 17 00:00:00 2001
From: Magesh Umasankar Creates a tar archive. The basedir attribute is the reference directory from where to tar. This task is a directory based task
-and, as such, forms an implicit Fileset. This
+and, as such, forms an implicit Fileset. This
defines which files, relative to the basedir, will be included in the
archive. The tar task supports all the attributes of Fileset to refine the
set of files to be included in the implicit fileset. In addition to the implicit fileset, the tar task supports nested filesets. These
-filesets are extended to allow control over the access mode, username and groupname
-to be applied to the tar entries. This is useful, for example, when preparing archives for
+filesets are extended to allow control over the access mode, username and groupname
+to be applied to the tar entries. This is useful, for example, when preparing archives for
Unix systems where some files need to have execute permission. Early versions of tar did not support path lengths greater than 100
+ Early versions of tar did not support path lengths greater than 100
characters. Modern versions of tar do so, but in incompatible ways.
-The behaviour of the tar task when it encounters such paths is
-controlled by the longfile attribute.
-If the longfile attribute is set to Note that this task does not perform compression. You might want to use the
+ Note that this task does not perform compression. You might want to use the
GZip task to prepare a .tar.gz package.fail
, any long paths will
-cause the tar task to fail. If the longfile attribute is set to
-truncate
, any long paths will be truncated to the 100 character
-maximum length prior to adding to the archive. If the value of the longfile
-attribute is set to omit
then files containing long paths will be
-omitted from the archive. Either option ensures that the archive can be
-untarred by any compliant version of tar. If the loss of path or file
-information is not acceptable, and it rarely is, longfile may be set to the
-value gnu
. The tar task will then produce a GNU tar file which
-can have arbitrary length paths. Note however, that the resulting archive will
-only be able to be untarred with GNU tar. The default for the longfile
-attribute is warn
which behaves just like the gnu option except
-that it produces a warning for each file path encountered that does not match
+The behaviour of the tar task when it encounters such paths is
+controlled by the longfile attribute.
+If the longfile attribute is set to fail
, any long paths will
+cause the tar task to fail. If the longfile attribute is set to
+truncate
, any long paths will be truncated to the 100 character
+maximum length prior to adding to the archive. If the value of the longfile
+attribute is set to omit
then files containing long paths will be
+omitted from the archive. Either option ensures that the archive can be
+untarred by any compliant version of tar. If the loss of path or file
+information is not acceptable, and it rarely is, longfile may be set to the
+value gnu
. The tar task will then produce a GNU tar file which
+can have arbitrary length paths. Note however, that the resulting archive will
+only be able to be untarred with GNU tar. The default for the longfile
+attribute is warn
which behaves just like the gnu option except
+that it produces a warning for each file path encountered that does not match
the limit.Parameters
@@ -63,9 +63,9 @@ the limit.
todo.html
are excluded.
<tarfileset dir="${dist.name}/.." mode="755" username="ant" group="ant">
<include name="${dist.name}/bootstrap.sh"/>
<include name="${dist.name}/build.sh"/>
- </tarfileset>
- <tarfileset dir="${dist.name}/.." username="ant" group="ant">
+ </tarfileset>
+ <tarfileset dir="${dist.name}/.." username="ant" group="ant">
<include name="${dist.name}/**"/>
<exclude name="${dist.name}/bootstrap.sh"/>
<exclude name="${dist.name}/build.sh"/>
@@ -166,7 +172,7 @@ fileset selects just the executable files. The second fileset must exclude
the executable files and include all others.
Note: The tar task does not ensure that a file is only selected -by one fileset. If the same file is selected by more than one fileset, it will be included in the +by one fileset. If the same file is selected by more than one fileset, it will be included in the tar file twice, with the same path.
Note: The patterns in the include and exclude
@@ -177,7 +183,7 @@ of a directory, so ${dist.name}
is a valid path relative
to ${dist.name}/..
.
Copyright © 2001 Apache Software Foundation. All rights +
Copyright © 2001-2002 Apache Software Foundation. All rights Reserved.