<processing> <job name="do xyz"> <os family="windows" /> <executefile name="$INSTALL_PATH/scripts/xyz.bat" workingDir="$INSTALL_PATH"> <arg>doit</arg><arg>$variable</arg> </executefile> </job> <job name="do xyz"> <os family="unix" /> <executefile name="$INSTALL_PATH/scripts/xyz.sh"> <arg>doit</arg><arg>$variable</arg> </executefile> </job> </processing>
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 value supports variable substitution, for example:
<env>MY_PRODUCT_HOME=$INSTALL_PATH</env>. The workingDir attribute for the <executefile> element adds the ability to set the working directory of the process spawned by the ProcessBuilder object, much as <env> elements refer to the environment object of ProcessBuilder.
The ProcessPanel now also supports configurable behaviour for the panel's "Previous" and "Next" buttons. By adding
<onSuccess> childs to the
<processing> element, you define which buttons you want unlocked in case of failure and in case of success, respectively.
<str id="UserPathPanel.required" txt="The chosen directory should exist."/> <str id="UserPathPanel.info" txt="Select the path: "/> <str id="UserPathPanel.browse" txt="Browse"/> <str id="UserPathPanel.exists_warn" txt="The directory already exists! Are you sure you want to install here and possibly overwrite existing files?"/> <str id="UserPathPanel.empty_target" txt="You have not specified a target location! Is this correct?"/> <str id="UserPathPanel.createdir" txt="The target directory will be created: " /> <str id="UserPathPanel.nodir" txt="This file is not a directory! Please choose a directory!"/> <str id="UserPathPanel.notwritable" txt="This directory can not be written! Please choose another directory!"/>