Message-ID: <1463394080.299192.1368972579048.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_299191_1612584460.1368972579048" ------=_Part_299191_1612584460.1368972579048 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
l allows you to execute arbitrary files after installation. The details for=
the compilation are specified using the resource
The XML file has the following format:
<job> may have the following attributes an
|(not set)||IzPack condition ID for= running the job||yes|
|(not set)||IzPack condition ID for ru= nning the job||no|
See the IzPack OS Restrictions tag.
In addition to
<arg> elements, =
<executefile> element also accepts
elements to set variables in the environment of the target process.=
This can be useful if this process requires some environment variables, su=
ch as its installation directory, to work properly. An
<env> element has the following syntax:
;/env>. Note the value supports variable substitution, for exampl=
workingDir attribute for the <executefile> element =
adds the ability to set the working directory of the process spawned by the=
=A0object, much as <env> elements refer to the environment object of =
The ProcessPanel now also supports configurable behav=
iour for the panel's "Previous" and "Next" buttons. By =
s to the
<processing> element, you define which buttons =
you want unlocked in case of failure and in case of success, respectively.<=
In the above example the job do xyz would be run, a=
nd if it returned with an error, the next button would be greyed o=
ut, and the button to the previous page would be enabled. If it re=
turned without an error, the conditions of the
<onSuccess> elements would be checked and the respective action would be taken.
<executecla= ss>- Execute Java Classes
It is also possible to execute = Java classes from this panel. Here's what this feature author (Alex Bradley= ) says:
> i've been able to work around my requirements by extendi=
ProcessPanelWorker functionality to run user-specified =
classes. i've extended the DTD of the
include a new element:
> i've also added a new sub-class of
executeclass. This will run a user-specified class=
in the context of the installer JVM with a single method :
> It can do everything i need and more. In particular, it= allows me to write a process extension and still be able to provide feedba= ck to the user through the feedback panel, and to add new functionality to = the installer, after its been built.
To use the executeclass facility= , you will need to create a jar file with your class and then add it to the= installer with the `The Jar Merging Element`.
<executeForPack>=- Only execute the job for certain packs
This can be be used=
to run the job only if the pack is enabled. For example, the batch file wi=
ll if either the
Executables packs are=
selected at install time.
<logfiledir>- Output of the processPanel saved t= o a log
New with version 3.7 is the possibility to tee output that i= s written to the ProcessPanel's textarea into an optional logfile. Using th= is feature is pretty much straightforward, you only have to add a line in <= code>ProcessPanel.Spec.xml that will tell IzPack the location, where= the logfile should be stored.
Variable substitution is performed, so=
you can use
$INSTALL_PATH as example.
The name of the l=
ogfile is not (yet) configurable but should fit in most cases. It will be n=
Here's an example:
This will generate a logfile named e.g.
004-11-08_19-22-20_43423.log located in
ProcessPanelWorker will write all output that is directe=
stderr to this file if
essPanel.Spec.xml contains the
= Please note that this one file is used for storing the complete output of a= ll jobs and not a file for each job that is run.------=_Part_299191_1612584460.1368972579048--