IzPack installation files try to preserve backwards compatibility as much as possible yet version 5.0 introduced some incompatible changes - mostly for consistency:
The <native>
elements must now be contained in a <natives>
wrapping element under 5.0. See the section on Native Libraries.
The IzPack installer will silently ignore the |
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.
<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> |
<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.
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.
This change applies from version 5.0.0-beta11, which is not yet released. LateShortcutInstallListener may not work at all in earlier 5.0.0 betas. |
Due to refactoring and improvement to the internal workings of IzPack, LateShortcutInstallListener
is no longer available. Instead, use the new <lateShortcutInstall/>
option in shortcutSpec.xml
. See Shortcut Specification for details.
IZPACK-798 changed TargetPanel.dir.* etc to be variables, rather than resources.
In 4.3.5, the default directory displayed in TargetPanel may be configured in a text file named:
In the <os name> form, the os name has been one of:
For 4.3.6, IZPACK-798 changed the above to use variables instead of text files, following the same naming convention.
For 5.0 a better approach would be to use Platform to determine the appropriate variable (see IZPACK-829).
For a more details, see Setting Default Installation Directories.
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.
Please note that also the configuration parameters and their default values have drastically changed, so in case you want to port your current maven build script you should consult the mojo class from the source tree for the current paramaters until a new Maven Plugin site has been published.