...
Name | Required | Description | Allowed Values |
---|---|---|---|
| yes | Determine at what point of installation the antcalls defined by element |
|
| no | Determine at what point of uninstallation the antcalls defined by element |
|
| no | Whether to log just warnings and errors, be quiet otherwise. | yes or no, default: no |
| no | Whether to log verbose information. | yes or no, default: no |
loglevel | no | Straight Ant log priority level mapping to the according log levels in Ant projects. | error, warning, info, verbose, debug |
| no | Path to the file where logging should be performed. Note: The logfile should be not marked for uninstallation otherwise it will be deleted too. | Any valid file path (TODO: should verify format) |
logfile_append | no | Whether to append to an existing log file (true) or create a new one / overwrite existing one (false). | true | false (default: false) |
| yes, if buildresource not specified | Path to the file which contains the antcall. This is the file you normally use as | Any valid file path (TODO: should verify format) |
| yes, if buildfile not specified | The value is the id of the resource which contains the antcall. This resource will be extracted out into a temporary file and the path to this file will be passed as if | A resource id. |
dir | no | The working directory for executing the Ant build in buildfile or buildresource . If set, it explicitly overrides the basedir set there and serves as base directory for relative path names accessed during the Ant build. | Any valid directory path |
| no | If it is defined, the message will be displayed in the InstallPanel whilst performing the ant call. | A string ID which refers to |
condition | no | Execute this action only if the condition is fulfilled. | A valid condition string. |
severity | no | The severity of an Ant action:
since: 5.0 RC5 |
|
In addition to the possible attributes there are some elements may be defined within an antcall element. All elements can be defined zero or more times in an <antcall>
. Although all elements are optional, no ANT tasks will be performed unless a <target>
element is specified. Do not confuse the following: "required"s are related to the attributes of the elements, not to the elements themselfs.
...