Message-ID: <972948846.40250.1371591480642.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_40249_606213802.1371591480642" ------=_Part_40249_606213802.1371591480642 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IzPack provides support to execute Ant tasks during installation= and uninstallation.
In the above:
an "extended" ant use needs more than one jar, for example often=
xercesImpl.jar. If an obscure "class not found" exc=
eption is raised during testing, check first for missing jar files.
stage attribute of the jar element determi=
nes when a jar is required. If an ant uninstaller custom action is used, th=
e uninstaller also needs the jar files. If
stage is "both=
" or "uninstall", the contents of the referenced jar file wi=
ll be packed into the uninstaller.
Note that not the jar file itself,=
but the contents of it are required. This implies, that the paths of the c=
ontained files are unique and the information in
will be lost.
An ant action is defined in the resource with the id "AntAct= ionsSpec.xml". In IzPack 5.0 (as of 5.0.0-beta-11), an XML-Schema is p= rovided, which may be declared as follows:
<= izpack:antactions version=3D"5.0" xmlns:izpack=3D"http://izpack.org/schema/antactions" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=3D"http://izpack.org/schema/antaction= s http://izpack.org/schema/5.0/izpack-antactions-5.0.xsd"> <!-- .... --> </izpack:antactions>=09=09
Prior to processing the packs a substitution is=
performed using all defined
IzPack variables on the spec file=
. This is a common way of loading spec files into custom actions.
more information see method
pec. If you want to substitute a value in the file, simply add a var=
iable via installData.setVariable in a custom panel before
el. The given variable name (id) should be written into the xml file=
in the common variable notation.
The following outlines the sections= available in the AntActionsSpec.xml:
The top lev=
el XML section is called
<antactions>. The antactions el=
ement may contain zero or more pack elements described below:
The pack element is used to tie the action(s) to be performed to the packs= selected in the installation. The pack element may have the following attr= ibute:
The name of the pack that this pack element m= aps to.=C2=A0 This should correspond to the name of a pack defined in insta= ll.xml
The pack element must contain = 1 or more antcall elements.
ement has the following attributes:
at what point of installation the antcalls defined by element
Determine at what point of uninstallation the an=
tcalls defined by element
To quit or not.
yes or no, default: no
To output verbose information or= not.
yes or no, default: 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)
yes, if build= resource not specified
Path to the fi=
le which contains the antcall. This is the file you normally use as
Any valid file path (TODO:= should verify format)
yes, if buildfi= le 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 <=
code>-buildfile were specified during the ant call via the command l=
ine. The temporary file is removed after the ant call. In this file variabl=
es are not substituted. For substitution there are properties in ant which =
can be used. Note: Never write an
A resource = id.
If it is defined, the message will be displayed in the InstallPanel whil= st performing the ant call.
A string =
ID which refers to
|no||Execute this action only if the condition is fulfill= ed.||A valid condition string.<= /td>|
In addition to the possible attributes th=
ere are some elements may be defined within an antcall element. All element=
s can be defined zero or more times in an
hough all elements are optional, no ANT tasks will be performed unless a
Defines a property to be = used with all targets and uninstall_targets which are defined for this antc= all.=C2=A0 The following attributes may be defined:
Allo= wed Values
The nam= e of the property to set.
Any string = value
The value t= o set for the property.
Any string va= lue
Defines p= roperties to be used, read from a property file which are defined for this = antcall.=C2=A0 The following attributes may be defined:
A= llowed Values
The = path to the properties file.
A valid = file path.
One way to fill specific d=
ata into it is to create a new file in a custom panel and fill it with valu=
es given by input fields. The file path can be set at installation time, if=
there is a variable in AntActionSpec.xml and an IzPack variable was define=
d before InstallPanel. That file can be only created with deleteOnExit, if =
<uninstall_target> was defined in this
all>. This implies, that other
<antcall>}}s can have =
<target>: target to=
call at installation h3. Targets to perform with this antcall at installat=
ion time. The targets should be defined in the given buildfile or else an a=
nt exception will be raised. This is that what you use, if you don't want t=
o perform the default target. e.g. cleaning the
The target to execute in th= e ANT build file during action specified in the order attribute of the antc= all (install time).=C2=A0 Note: Multiple targets to execut= e for the action may be specified by using multiple target elements.=C2=A0 = The following attribute must be defined:
Allowed Values= p>
Name of the target = to execute in the ANT buildfile
Any v= alid ANT target defined in the build file.
Targets to perform with this antcall a= t uninstallation time. Note: Multiple targets to execute f= or the action may be specified by using multiple target elements.
Name of the target to execute in the ANT buildfile
Any valid ANT target defined in the build file.= td>