Upgrading
...
installation files
IzPack installation files try to preserve backwards compatibility as much as possible yet version 5.0 introduced some incompatible changes - mostly for consistenencyconsistency:Known incompatibilities are:
Native elements
The <native>
...
elements must now be contained in a <natives>
...
wrapping element under 5.0. See the section on Native Libraries.
| Warning | ||
|---|---|---|
| ||
The |
...
IzPack installer will silently ignore the |
...
tags contained inside a |
Panel action param elements
| Warning |
|---|
This change applies from version 5.0.0-beta11, which is not yet released. |
The optional <param> element in a panel <action> element now uses name and value attributes instead of key and value child elements. The following examples illustrate the change between the two versions.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<panel classname="TargetPanel" id="target.win">
<os family="windows" />
<actions>
<action stage="preactivate" classname="com.opentext.installer.actions.RegistryReaderAction">
<param>
<key>ConfigurationFile</key>
<value>RegistryReaderConfiguration.xml</value>
</param>
</action>
</actions>
</panel> |
| Code Block | ||||
|---|---|---|---|---|
| ||||
<panel classname="TargetPanel" id="target.win"> <os family="windows" /> <actions> <action stage="preactivate" classname="com.opentext.installer.actions.RegistryReaderAction"> <param name="ConfigurationFile" value="RegistryReaderConfiguration.xml"/> </action> </actions> </panel> |
See the section on Panel Actions.
Panel configuration param elements
| Warning |
|---|
This change applies from version 5.0.0-beta11, which is not yet released. |
The optional <configuration> section in a <panel> element permits nested <param> elements. Previously, the <param> element was specified using child elements <key> and <value>. This has now been changed to name and value attributes - see Panel action param elements, above, and the Panels section.
Upgrading customizations
Prepare to detect some internal refactorings when providing customizations: e.g. the class com.izforge.izpack.util.AbstractUIProcessHandler can now be found under com.izforge.izpack.api.handler.AbstractUIProcessHandler
Using the IzPack Maven Plugin
Release 5.0 of IzPack introduces a new implementation of the izpack-maven-plugin currently found at http://izpack.codehaus.org/izpack-maven-plugin/. In contrast to the documentation there, an explicit dependency to the izpack-standalone-compiler is no longer needed.
...