IzPack now supports InstallerRequirements

The current trunk version of IzPack now supports the so called installer requirements. This means that it's now possible to define requirements for being able to start the installation. E.g. if a certain user has to start the installer, this will be checked by using a UserCondition with an installer requirement. If the condition is not fulfilled, a message will be shown and the installer exits.

Article Flexible installations with IzPack in Java Magazin 07.08

I published an article about flexible installations with IzPack 3.11 in the current issue (07.08) of Java Magazin. Full quellcode for a sample project is included.

IzPack 4.0 released

The next version of IzPack was released today. It's the first one developed within the codehaus infrastructure.
For a feature overview click here.

How to debug variables and conditions in IzPack

From IzPack 3.11 on, there's a built-in debugger for variables and conditions. The debugger is activated when the installer is called with -DTRACE=true as JVM option.

Ex.1:

java -DTRACE=true -jar myInstaller.jar

The debugger shows up as a panel in the east of the InstallerFrame or if the guiModifier showDebugWindow is set to true, it will show up as seperate window.

Ex.2:

<modifier value="true" key="showDebugWindow">

IzPack now has built-in conditions

IzPack now has built-in conditions which means, that there are some predefined conditions which can be used in the installer. These conditions are:

• izpack.windowsinstall


• izpack.linuxinstall


• izpack.solarisinstall


• izpack.macinstall

There's also a PackSelectionCondition for every pack. The Ids for these condition will be built up from the pack id or if not specified, the pack name. If there's a pack called Testpack with id test.pack, there will be a condition called izpack.selected.test.pack