Name
ear
Synopsis
Creates Enterprise Application Archive (EAR) files. Although the
jar
task is also capable of creating EAR files,
the ear
task simplifies the process. EAR files are
the deployment mechanism for J2EE applications, and are little more
than JARs consisting of well-defined directories and files.
Attributes
-
appxml
(1.4, File, Y) Specifies the location of the deployment descriptor, which is always renamed to
META-INF/application.xml
in the generated EAR file. The source file does not have to be namedapplication.xml
.-
basedir
(1.4, File, N) Specifies the base directory from which to add files to the EAR file.
-
compress
(1.4, boolean, N) If
true
, compress the EAR file. Defaults totrue
.-
defaultexcludes
(1.4, boolean, N) Determines whether to use default excludes, as described in Chapter 4 under “FileSet DataType.” Defaults to
true
.-
earfile
(1.4, File, Y) Specifies the name of the EAR file to create.
-
encoding
(1.4, String, N) Specifies the character encoding for filenames inside the EAR file. Defaults to UTF-8. The Ant specification warns that changing this attribute probably renders the EAR file unusable by Java.
-
excludes
(1.4, String, N) A comma-separated list of file patterns to exclude. These are in addition to the default excludes.
-
excludesfile
(1.4, File, N) The name of a file containing one exclude pattern per line.
-
filesonly
(1.4, boolean, N) If
true
, do not create empty directories. Defaults tofalse
.-
includes
(1.4, String, N) A comma-separated list of file patterns to include. ...
Get Ant: The Definitive Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.