Creating the War files using the ANT Scripts

text zoom

Previous: Example to Create the Jar files Ear Command in Ant :Next

This task is an extension to jar task. The war file is a web archieve file in the java environment and is ready to deploy on the web servers. The War task is a shortcut for specifying the particular layout of a WAR file.

The following table will demonstrate the attributes for the war task.

Attribute	Description	Required
destfile	the WAR file to create.	Exactly one of the two.
warfile	Deprecated name of the file to create -use destfile instead.
webxml	The servlet configuration descriptor to use (WEB-INF/web.xml).	Yes, unless needxmlfile is true, the file is pulled in via a nested fileset, or an existing WAR file is being updated.
needxmlfile	Flag to indicate whether or not the web.xml file is needed. I=it should be set to false when generating servlet 2.5+ WAR files without a web.xml file. Since Ant 1.7	No -default "true"
basedir	the directory from which to jar the files.	No
compress	Not only store data but also compress them, defaults to true. Unless you set the keepcompression attribute to false, this will apply to the entire archive, not only the files you've added while updating.	No
keepcompression	For entries coming from existing archives (like nested zipfileset s or while updating the archive), keep the compression as it has been originally instead of using the compress attribute. Defaults false. Since Ant 1.6	No
encoding	The character encoding to use for filenames inside the archive. Defaults to UTF8. It is not recommended to change this value as the created archive will most likely be unreadable for Java otherwise.	No
filesonly	Store only file entries, defaults to false	No
includes	comma- or space-separated list of patterns of files that must be included. All files are included when omitted.	No
includesfile	the name of a file. Each line of this file is taken to be an include pattern	No
excludes	comma- or space-separated list of patterns of files that must be excluded. No files (except default excludes) are excluded when omitted.	No
excludesfile	the name of a file. Each line of this file is taken to be an exclude pattern	No
defaultexcludes	indicates whether default excludes should be used or not ("yes"/"no"). Default excludes are used when omitted.	No
manifest	the manifest file to use.	No
update	indicates whether to update or overwrite the destination file if it already exists. Default is "false".	No
duplicate	behavior when a duplicate file is found. Valid values are "add", "preserve", and "fail". The default value is "add".	No
roundup	Whether the file modification times will be rounded up to the next even number of seconds. Zip archives store file modification times with a granularity of two seconds, so the times will either be rounded up or down. If you round down, the archive will always seem out-of-date when you rerun the task, so the default is to round up. Rounding up may lead to a different type of problems like JSPs inside a web archive that seem to be slightly more recent than precompiled pages, rendering precompilation useless. Defaults to true. Since Ant 1.6.2	No
level	Non-default level at which file compression should be performed. Valid values range from 0 (no compression/fastest) to 9 (maximum compression/slowest). Since Ant 1.7	No