AntFetch
AntFetch
AntFetch is identical to the standard ‘Ant’ task, except that it allows properties from the new project to be set in the original project.
Some background may be in order: When the
Suppose that the “fillImageDirectory” target sets a property named “image.directory” and I call the following:
<ant dir="${image.project}" target="fillImageDirectory"/>
<echo>${image.directory}</echo>
The output of the echo task will be ${image.directory}, not whatever was set in the “fillImageDirectory” target. The AntFetch task allows that image.directory property to be set in the original project. The attributes for AntFetch are identical to the ‘Ant’ task, with one additional, optional attibute. This attribute is named “return” and can be either a single property name or a comma separated list of property names.
Assuming that “fillImageDirectory” actually sets a property named “image.directory”, the following example will print out the directory name:
<antfetch dir="${image.project}" target="fillImageDirectory" return="image.directory"/>
<echo>${image.directory}</echo>
And this one will also print out the thumbnail directory:
<antfetch dir="${image.project}" target="fillImageDirectory" return="image.directory, thumbnail.directory"/>
<echo>${image.directory}</echo>
<echo>${thumbnail.directory}</echo>
The attributes for AntFetch are identical to the ‘ant’ task, with one additional, optional attibute. This attribute is named “return” and can be either a single property name or a comma separated list of property names.
Table 14.1. AntFetch Attributes
Attribute | Description | Default | Required |
---|---|---|---|
return |
A comma separated list of property names. Whitespace is allowed, so either “a,b” or “a, b” are acceptable. | None | No |
For other attribute and nested element information and more examples, see the documentation for the “ant” task in the Ant documentation.