...
Each <job> may have the following attributes and an <os> attribute:
| Attribute | Default | Description | Mandatory |
|---|---|---|---|
name | (not set) | name given to the step the job | yes |
condition | (not set) | IzPack condition ID for running the job | no |
| catch | false | Job runs only in the event of other jobs failing | no |
| final | false | Job runs always, whether previous jobs succeed or not | no |
Catch and Final jobs
The 'catch' and 'final' attributes for a process panel job are used to create a try/catch/final structure for your processes. If a standard job (one without catch or final) fails, the process panel will skip the remaining jobs and exit with a failure.
...
<executeFile>- Execute Shell Scripts
The executeFile element has the following attributes:
| Attribute | Value | Default | Description | Mandatory |
|---|---|---|---|---|
name | string | (not set) | Name of the file to execute | yes |
workingDir | string | (not set) | Working directory of the process spawned by the ProcessBuilder object | no |
| onError | ask | fail | ask | Controls the behaviour when the file exits with a non-zero exit code. ask: Prompt the user whether or not to continue. fail: Do not allow continuation. Since: IzPack 5.1.0 | no |
In addition to <arg> elements, the <executefile> element also accepts <env> elements to set variables in the environment of the target process. This can be useful if this process requires some environment variables, such as its installation directory, to work properly. An <env> element has the following syntax: <env>variable=value</env>. Note the element supports variable substitution, for example: <env>MY_PRODUCT_HOME=$INSTALL_PATH</env>.
...