install4j releases

install4j Release 4.2.3

Thu, 18 Jun 2009 09:00:00 +0200

New features:

Added a "Visibility script" to all form components that determines if a form component is shown or not, invoked in both GUI and console modes
"Install files" action: Added an "Update bundled JRE" property that allows to prevent the update of an already installed bundled JRE
Mac OS X: If defined, use the environment variable INSTALL4J_ARGUMENTS for the command line arguments
Installer, Uninstaller and custom installer applications: Added "Windows console executable" property to create executables that open a console and support installations via rsh
"Directory chooser" and "File chooser" components: Added a "Validation script" property that can reject user selections performed via the chooser button
Unix installers: If the environment variable INSTALL4J_TEMP is defined, it is used as the base directory for self-extraction
"Create a file association" action: Added an "Additional parameters" property for additional arguments to be passed to the launcher if invoked via the file association
API: Added com.install4j.api.beans.ReplacementMode#PROPERTIES_FILE
API: Added com.install4j.context.Context#getMessage(String, Object[]) to avoid explicit use of java.text.MessageFormat
Installer applications: Added "Custom watermark text" property

Bugs fixed:

Critical: The 1.6 JRE contained in Mac OS X 10.5 Update 4 does not work with installers created by previous versions of install4j. This affects all projects with a minimum Java version of 1.6.
File and directory chooser form components: An empty initial value for the file was displayed as the working directory in console mode
com.install4j.api.screens.Screen#willActivate() was called before the "Pre-Activation" script
Non-existent parent directories in -Dinstall4j.alternativeLogfile were not created
"Register Add/Remove item" action: Use current user registry for add/remove entry if system registry is not writeable
"Installation components" screen: Fixed default selection in console mode when screen was shown multiple times
"Installation components" screen: Wrong tooltip was shown if help button was not shown
"Installation components" screen: Improved deselection behavior of component folders containing components that depend on each other
"Installation components" screen: Selection state of component folder containing dependent components was not always correct
"Save installer variables to the Java preference store" action: Package name containing underscores were not supported on Unix
Add short name of project to the log file names in the TEMP directory so they can be identified more easily
Form components with labels: Custom icons were not displayed in the uninstaller
Form component screens: Relative external files were not correctly resolved in preview
Calls to com.install4j.api.context.WizardContext#setNextButtonText(String) and similar methods did not enlarge the button if necessary
"Replace installer variables in a text file" action: Property "Escape for properties file" had no effect
Installation directory selector: On Windows, if the drive letter or the UNC share did not exist, the error message shown to the user mentioned a permission problem
Files that were not overwritten due to an overwrite policy were logged as an error in the installation.log file

install4j Release 4.2.2

Fri, 17 Apr 2009 09:00:00 +0200

New features:

"Execute launcher" action: added "Arguments" property
Unix installers: If the environment variable INSTALL4J_KEEP_TEMP=yes is set, the temporary files are not deleted
Added an $OUTFILE variable for code signing in case the signing command cannot overwrite the original executable

Bugs fixed:

"Display progress" screen: Installer variables in title and subtitle properties were not replaced
"Show PDF" action and "Display PDF file" screen: PDFs were shown with a red cross
"Register Add/Remove Item" action: Multiple installations of the same installer into different directories would only produce a single item in the software registry
"Display text" screen: If "Info text" property was empty, a blank space was left above the text area
"Install Files" action: Do not check for running processes if "Install runtime" is not selected
"Execute launcher" action and "Show URL" action: On some Linux distributions the launched process could be killed if the installer was terminated immediately
Screens could not be added to an empty screen group in the uninstaller
Files in file sets that were excluded for a media file were accessed at compile time
Code editor: JDKs installed directly under c:\ on Windows could not used for code completion
Fixed class cast exception at runtime that occurred when using action groups under certain circumstances
Fixed FileNotFoundException at runtime that occurred when the installer exited under certain circumstances
Unix: Installer did not terminate correctly if gunzip does not exist
Windows: Temporary installer log files were not deleted when an error occurred
Windows: If the GUI cannot be displayed due to a broken JRE, a message about an "X-server" was displayed
Windows 98: Automatic proxy detection lead to a runtime error
Windows 98: Setting an environment variable could lead to a runtime error
API: Mac OS X: com.install4j.api.SystemInfo.getPhysicalMemory returned wrong result for machines with more than 2 GB RAM

install4j Release 4.2.1

Fri, 6 Feb 2009 09:00:00 +0100

New features:

Create program group action: Added a "Fail if symlinks are not created" property
"Uninstall previous installation" action: Added properties "Installation directory" and "Only if the same application ID is found" to be able use the action for different and multiple previous installation directories.

Bugs fixed:

Do not show the "Create program group" screen on Unix if the "Create symlinks on Unix" property in the "Create program group" action is not selected
A ClassNotFoundException could be thrown in the uninstaller on Linux when no mouse movement was made before the bundled JRE was deleted
"Run executable or batch file" action: Do not quote arguments without special characters in them (regression in 4.2). This affects batch files only.
If the -include-options feature introduced in 4.2 was used, launcher scripts did not work on Solaris
"Modify an environment variable on Windows" action: Fixed various problems on uninstallation
"Update schedule selector" form component: No question was asked in console mode
Unix: Always prevent error messages from the preference store subsystem from being logged to the console
The debug attribute of the install4j ant task as described in the documentation did not work
Uninstallation of installer files from a sibling directory of the installation directory whose name starts with the name of the installation directory did not work
Additional localization files with java.util.Properties format (ending in .properties) were locked while the install4j IDE was open
Using backslashes in file names on Unix could lead to an error while saving the project
For long-running startup actions, the installer could exit with a timeout
Compiler variables did not work correctly in the executable name and executable directory properties of the uninstaller

install4j Release 4.2

Tue, 20 Jan 2009 09:00:00 +0100

New features:

Support for including other .vmoptions files
Support for including other .vmoptions files with the new -include-options [path to .vmoptions file] VM parameter. This works in the fixed VM parameters as well as the .vmoptions files.
Improved persistence of installer variables
Added a "Save installer variables to the Java preference store" action that saves selected installer variables that can be encoded as strings
Added a "Load installer variables from the Java preference store" action
Launcher API: com.install4j.api.launcher.Variables offers methods to get compiler and installer variables in the launcher and to load and save installer variables from the Java preference store
Launcher API: com.install4j.api.launcher.Variables offers methods to access the installer and compiler variables of the installer
Support for loading response files in the installer
Added a "Load response file" action
Default installer template: Added a "Load response file" action to the "Installation directory" screen to load user input from a previous installation
Default uninstaller template: added a "Load response file" action to the startup sequence to load user input from the installer
Improved proxy handling and server side authentication
The proxy settings of the default browser are now used on Windows for all downloads
"Check for update" and "Download file" actions: Added "Ask for proxy if necessary" property. If deselected and the download fails, no proxy dialog will be displayed.
Added installer parameters -Dinstall4j.clearProxyCache=true and -Dinstall4j.showProxyConfig=true to control the proxy cache
Server side authentication for downloads is now supported. A dialog for entering user name and password is displayed if the web server requires authentication.
Console access for Windows GUI launchers
Windows GUI launchers: Added an optionally recognized -console parameter that connects stderr, stdout an stdin to the console from which the launcher was invoked
Visual progress for unattended execution
Added the option -splash [title] for installer applications that brings up a small progress window if unattended mode is selected with the -q option
Added a -wait [timeout in seconds] command line option for installers. In unattended mode on Windows, the installer application will wait for all launchers and installer applications to shut down before starting the installation. If the timeout is reached, it will exit with an error message.
Added a filter field in registry dialogs for screens, actions and form components
Tool bars now show icons with text. This setting can be changed by right-clicking a tool bar.
Show missing files in the distribution tree and on the custom code tab in red
Mac OS X: The principal language is now written to the Info.plist file
Added a "Missing files at build time" option to "General Settings->Media File Options" that determines the action if a file or directory in the distribution tree is missing. The default setting is now "Print a warning and continue".
Added a "Scan directory" entry type on the Installer->Custom code tab
All signed JAR files can now be packed with the Pack200 compression (with a lower compression ratio due to a single segment being used)
If the "Safe back button" policy is set for a screen, a back button is also displayed if all actions in the previous screen are configured for multiple execution
Updater templates: Execute downloaded installers in unattended or console mode depending on how the updater was invoked.
Do not set native look and feel for installer applications if the -Dswing.defaultlaf VM parameter is set
Added an installer variable sys.preferredJre that is set after the "Install Files" action has run and contains the path to the JRE that will be used by the installed launchers.
Added a compiler variable sys.applicationId that contains the application ID of the project
If possible, the language selection dialog of a multi-language installer is now displayed in the system language rather than the principal language. There is a new option on the "Languages" tab to always use the principal language.
Redirection files of launchers: Absolute paths and environment variables are now supported
"Single radio button" form component: Added "Selection script" property to execute code when the user clicks the radio button
Added "Default execution mode" property for all installer applications to be able to configure console or unattended execution as the default mode.
Added "Fall back to console mode on Unix" property for all installer applications. This is selected by default and switches to console execution mode if no X server is available.
Added a "Replace installer variables in a text file" action. Compiler variables and i18n keys are also replaced by this action.
Added a "Fail if no replacement occurred" property to all actions that modify files
"Copy file" and "Move file" actions now also work with directories and have been renamed accordingly
"Run executable or batch file" action: Environment variables can now be set or modified
"Run executable or batch file" action: Added "Show windows console" and "Keep console window" properties for Windows in order to show a console window with the output or the executable and optionally keep the console window open
"Create program group" action: Added separate options to disable the creation of Unix symlinks and Unix menu entries
The "Create start menu entry" action now also works on Linux/Unix
"Modify an environment variable on Windows": The changes are now reverted on uninstallation, this behavior can be controlled with the new "Revert on uninstallation" and "Only if not modified" properties.
API: com.install4j.api.context.WizardContext now has methods to set the text of the navigation buttons
API: added com.install4j.api.UpdateUpdateDescriptor.checkVersion(String version) to check if a version is compatible with the minimum and maximum versions of an update descriptor entry
API: Property customizers can now be built with the new classes com.install4j.api.beaninfo.PropertyConverter and com.install4j.api.beaninfo.PropertyCustomizers
API: Properties of type java.util.LinkedHashMap get a default editor in the IDE if they are registered with the Install4JPropertyDescriptor.CONTEXT_STRING_TO_STRING_MAP context

Bugs fixed:

Help text in property pane on Screens & Actions tab was black on some Vista installations
Using a splash screen image in PNG format with an alpha channel lead to a compilation error
.vmoptions files on Unix: leading spaces on a line were not ignored
Actions could sometimes not be added to screens in the uninstaller
Mac OS X: Service were started as the original user if "Restart as root" was selected in the "Require admin user" action
The directory name for the uninstaller was sometimes not saved to the project file under some circumstances
The uninstaller used the "Custom image for title bar" property from the installer
Fixed "Run executable" action on Vista when path contains special characters
"Run executable" and "Execute launcher" actions: stderr and stdout were not consumed by default
Version comparison for com.install4j.api.updateUpdateDescriptor.getPossibleUpdateEntry() has been improved
"Show URL" and "Show file" actions did not always work on Finish screen on Linux / Unix
Line endings in .vmoptions files were not adjusted correctly for Windows media files
"Single radio button" form component: installer variables were not replaced in the "Radio button label" property
Proxy dialog was not big enough in some look and feels
Do not warn or fail during a build if a missing file or directory has been excluded for the media file
"Create program group" action on Unix: Do not create symlinks in the same directory as the destination file, thereby overwriting the destination file
Downloads failed if the wen server reported an unknown file size
"Modify an environment variable on Windows" action: If "prepend" or "append" were selected for the "Modification type" property, the variable separator ";" was not inserted if the environment variable already contained a value
"Create program group" action on Unix: Symlinks were also created for launchers for which menu integration has been disabled
Fixed performance regression in code editor on Windows if JRE 1.6.0_10+ is used
Improved error reporting in installation log for actions that modify files
The -c and -console parameters did not have any effect on Windows for installer applications other than the installer itself
"Delete a node or key in the Java preference store" action: If the key or node did not exist, the action did not fail
Added an installer variable "sys.responseFile" that contains the path of the response file if a response file has been specified on the command line with the -varfile option.
Windows program group was always set to default value even if a response file was specified on the command line
"Installation directory chooser" form component: In console mode, the installation directory was not changed
"Installation type screen": The associated label was not selected if the radio button was selected
Multi-line string properties could sometimes not be reset to an empty value
Mac OS X. CMD+Q was not handled in the installer
Pack200 compression could produce archives with a Java 1.6 version number for some archives even if the minimum version of the project was set to 1.5
If there were multiple media output directories, the update descriptor updates.xml was only copied to the last one
Java editor: There were empty entries in the completion popup for constructor parameters
"Radio button group" form component: The initially selected index was not applied from a response file
Running the command line compiler with a relative path name for the config file did not correctly resolve resources
Java 5 syntax was underlined as an error in the editor on Mac OS X even if the Java minimum version for the project was set to 1.5 or higher

install4j Release 4.1.5

Thu, 30 Oct 2008 09:00:00 +0100

New features:

"Installation components" screen: An installation directory chooser can now optionally be displayed on this screen
Added an "Installation directory chooser" form component in the "Special selectors" category
Compiler variables are now also supported in the media output directory and in custom code entries
"Install files" action: Added "Installation size calculator" script for changing the minimum required size for the installation. This value is also reported by the "Installation directory" screen.
"Install files" action: Added "Install runtime" property. If you deselect this option, the installation directory will not be created and the runtime will not be installed. This is useful for installers that just modify some existing directories.
"Directory selection" screen: Added "Allow spaces in directory name" property for Unix installers
"Display license" screen: Added "User must scroll to bottom" property
It is now possible to user compiler variables that are only defined in an external variable file (passed to the command line compiler with the -f or --var-file parameter) and that are not defined in the project
The -f or --var-file command line parameter now supports a list of variable files, separated with semicolons, e.g. --var-file=one.properties;two.properties
"Check box" form component: Added "Selection script" property to execute code when the selection is changed
Added VM parameter -Dinstall4j.alternativeLogfile=[path] to copy installation log file to an arbitrary location after the installer has finished without moving the log file to the installation directory
Added "Create log file for stderr output" property for installer. stderr redirection can now be switched off by deselecting this property.
The file name and the the directory of the uninstaller are now customizable
Leading labels in all form components are now baseline-aligned with the center component when Java 6 or higher is used
API: Added support for organizing properties in a tree with com.install4j.api.beaninfo.Install4JPropertyDescriptor#setParentProperty
API: Properties can be hidden depending on the value of their parent property with com.install4j.api.beaninfo.Install4JPropertyDescriptor#setVisibilityDiscriminator
API: added focusNextButton() to the com.install4j.api.context.WizardContext

Bugs fixed:

Setting the program group via the API did not work correctly multiple times when the "Create program group" screen was also present
Windows exe version information: The legal copyright was not set for installer, now it is set to the publisher
Windows exe version information for uninstaller and custom installer applications was not set
The uninstaller executable was installed even if the uninstaller was disabled on the screens & actions tab
Linux/Unix: Fixed startup failure with OpenJDK 1.6.0_10 or higher when compiz is running
"Install Service" Action: When adding this action, the icons in the screens & actions tree could disappear under some circumstances
"Modify class path" action: Installer variables were not replaced in the class path entries
"Recent Projects" menu was always empty on Mac OS X
Many keyboard shortcuts were not suitable on Mac OS X
Linux/Unix services: The output from nohup is now redirected to /dev/null
Newly added screens in the uninstaller were added above the "Startup" sequence
Workaround for erroneous virus definition in CA Anti-Virus 2009

install4j Release 4.1.4

Fri, 22 Aug 2008 09:00:00 +0200

New features:

It is now possible to access environment variables at build-time with the syntax ${compiler:env.variableName}
Improved output of com.install4j.api.Console.more(). This also affects the "Display License agreement" and similar screens in unattended mode.
Do not append or prepend a value to environment variables on Windows if the appended or prepended value is already contained in the environment variable. This affects API methods in com.install4.api.windows.WinEnvVars as well as actions that modify environment variables.

Bugs fixed:

"Modify a text file with regular expressions" action: "Escape for property file" property did not work for chars > 127
"Add a desktop link" and "Create quick launch icon" actions: Installer variables were not replaced in "Arguments" and "Tooltip description" properties
"Replace text in XML file" action: Fixed NPE if system ID in doctype oft the XML document was not set
Custom uninstaller icon was not used
Exceptions in "Run script" actions were not annotated with the bean path
Launching the install4j IDE from an upgrade installer could fail if used with a floating license
The uninstaller of a 4.0 installation did not work after 4.1 add-ons were installed
Help texts in property panes were not readable if the Windows classic look and feel was enabled
Language auto-detection did not work if principal language was any language other than English
Fixed Pack200 compression of JAR files that contain other JAR files
Adding additional locales to the resource/messages/languages file required addition of new locale names to all used i18n properties file for multi-language installers to work
Fixed NPE for single radio button form component in console mode when there was no initial selection
Group conditions were not re-evaluated when moving back and forth
Installer log files were not created after canceling the installer if there no actions were executed after a rollback barrier
Custom installer applications always showed language selection dialog for multi-language installers
Variables at the start of a download URL were not accepted in the "Bundled JRE" step of the media wizard
Unix: Links for launchers were also created if they were contained in unselected installation components
Mac OS X: "Execute Launcher" action: If the installer required admin privileges, the launcher was started as root and not as the original user
Mac OS X: If the installer required admin privileges, daemons were started as root and not as the original user
Mac OS X: Buttons on password dialog were not localized
Mac OS X: Fixed detection of Java 6 when it was not selected as the default JRE
Mac OS X: Fixed problems with startup items when the installation path contained spaces

install4j Release 4.1.3

Thu, 5 Jun 2008 09:00:00 +0200

Bugs fixed:

The updater templates "Updater with silent version check" an "Updater without version check" were broken
Fixed regression with launchers in subdirectories for folder installers on OS X

install4j Release 4.1.2

Tue, 3 Jun 2008 09:00:00 +0200

New features:

API: added com.install4j.api.Util.isWindows2003()

Bugs fixed:

"Display text" screen: The "Screen subtitle" property instead of the "Info text" property was used for the label above the text area
"Services" screen: Launcher file paths displayed on Linux/Unix could have wrong file separator character
"Check box" form component: Initial selection and text were set after the initialization script ran. This has been reversed.
"Apply an XSLT transform" action: Source file did not refer to its installed location
"Create program group" screen: If a program group was selected in the list and the create shortcuts for all users check box was toggled, the list was not updated with the new content
"Create program group" screen: Multiple selection was possible in the list of program groups
"Create program group" action: Installer variables were not replaced in arguments of additional program group entries
Screens displaying HTML text: Some HTML files could make the installer hang
Fixed problems when defining installation components with non-default file sets
Included JRE was not used for language restart
Code editor: Exception was thrown when opening the code editor and the custom code contained duplicate entries
Code editor: Keyboard shortcuts on Mac OS X inserted additional character
Generated launchers in non-default file sets did not work correctly
Fixed problem with missing JRE extensions on AIX
Could not delete additional languages under General settings->Languages

install4j Release 4.1.1

Thu, 24 Apr 2008 09:00:00 +0200

New features:

Added VM parameter -Dinstall4j.logEncoding=... for installers to set the encoding of the log file to something other than the default encoding
Added a "--faster" command line and ant task option for disabling LZMA and Pack200 compression

Bugs fixed:

Main class selector in the launcher wizard did not work anymore
Code editor did not work with the Java look and feel (Metal)
Code editor: When completion popup was shown more than once, mouse selection was not possible
Code editor: accepting a code completion proposal with a double click was not possible
Script compiler used default encoding, so that all characters in scripts that were not representable by the default encoding were replaced with question marks
"Execute launcher" action: Did not work for external launchers with installer variables in the path name
"Create program group" action: Links for external launchers with installer variables in the path name were not resolved correctly
"Delete a file or directory action": If the "recurse into directories" option was selected, and the temporary and target directories were on different volumes, all directories were not deleted
Fixed exception on Mac OS X for launchers installed with older versions of install4j
Design time JDKs were not supported on Mac OS X
When clicking the window close button on a screen with the "Quit after screen" property selected, the installer was not finished just like when clicking the "Finish" button

install4j Release 4.1

Thu, 3 Apr 2008 09:00:00 +0200

New features:

New Java code editor with code completion, Javadoc and problem analysis
Auto-update functionality
Custom installer applications
Action and screen groups
Redesigned screens & actions tab
Code gallery with example scripts
File sets in the distribution tree
Support for Java 6 splash screens
Optional comments on all installer elements
Installation types
PDF screen and action
Actions for changing Windows access rights
New form component "Single radio button". You can configure coupled form components that are enabled or disabled depending on whether the radio button is selected.
New form component "Multi-line HTML label". This component supports http and file links.
New form component "Key value pair" form component". This consists of a leading label and a center label.
New form component "Hyperlink action label". Instead of showing a URL, you can configure an action script that is executed if the user clicks on the link.
New form component "Progress display". This form component can show the progress of actions attached to the containing form screen.
New action "Sleep". Do nothing for a specified number of milliseconds.
All installer elements can now be disabled. Disabled elements will not be included in the build and will not be validated.
Improved error reporting: At run time, if a script throws an exception, the property name, the name of the bean as well as the names of any enclosing beans are reported.
XML actions: Added XML parser properties "Validating" and "Download external entities" for xml actions
Design time JDK: The same JDK/JRE that is configured for the Java code editor is used for script compilation. This only applies to the runtime library rt.jar, the compiler is bundled with install4j.
"Create program group" action: Redesigned configuration of Windows program group entries
Installer variables with array values in all string list properties are expanded as separate arguments. See the "List" form component in the jdkSelection sample project for an example.
"Installation Location" screen and "Directory chooser" form component: Added property for allowing spaces in directory name for Unix/Linux installers.
"Install files" and "Install contents of ZIP file" actions: Added "Delay if necessary" and "Trigger reboot if required" properties for installing on top if used files in Windows.
"File associations" screen: Added "Show selection buttons" property for showing buttons that select and unselect all associations.
"Display text" and "Display information" screens: Added HTML preview tab in editor
Java 6+: Use Java 6 Console API for reading passwords in console installer
All installer elements including single actions can now be excluded in the "Customize project->Exclude installer elements" step of the media wizard.
Font properties in form components: Possibility to use "0" as font size to get default size. Font name "dialog" yields the default label font.
"File chooser" and "Directory chooser" form components: Added property "Manual entry allowed"
"Set a variable" action: added "Fail if null" property
"Display progress" screen: Added "Initial status message" property
Improved many messages in the launcher and the installer
"Installation directory display": Display free disk space
Windows launchers can now request heap sizes (-Xmx values) of the same maximum size as the default java launchers if the built-in splash screen is not used. Previously the maximum size was reduced due to fragmentation of the address space.
Custom localization files are now reloaded in the IDE when they are changed externally
Consistent keyboard accelerators in the install4j IDE
Consistent display of IDs in the install4j IDE: If ID display is enabled for a view, the ID is shown in brackets after the element.
ID display settings are persistent across restarts of the install4j IDE
IDs can be printed in the project export by selecting the "Export IDs" check box in the file chooser
"List", "Drop-down list" and "Combo box" form components: Added "Selection change script" property that is invoked when the user changes the current selection
Added "Scrollable" property for customizable form screens. After de-selecting this property, you can assign remaining vertical space to vertically scalable components such as text areas or lists.
"Text area" and "List" form components: Added "Fill extra vertical space" property
Scripting: Added methods to wizard context to make selected navigations buttons invisible
Scripting: Added formEnvironment script parameter to all script properties of form components
Scripting: Added context.goBackInHistory(Screen targetScreen) to move back to a specific screen in the history rather than in the screen sequence
Scripting: A reboot can now be triggered with context.triggerReboot()
Scripting: Added formEnvironment.resetFormComponents() in order to reset components in loops
Scripting: Added formEnvironment.saveFormComponents() to validate and save form components, e.g. for a button form component which needs current values of variables.
Scripting: Incompatible change (very low impact): Script parameters are now final which allows them to be used directly in anonymous classes.
Scripting: Added "Pre-activation" and "Post-activation scripts" to screens.
Scripting: Added ApplicationRegistry.getAddOnApplicationInfoByDir() to get information about installed add-on installers
Scripting: Added method requestFocus() method to FormComponent interface
API: Incompatible API change (very low impact): Introduced FormPanelContainer to make form panels more configurable. This replaces the Screen#hasFormPanel() and Screen#setFormPanel(...) methods.
API: Form components can request remaining vertical space by returning true from the new interface method FormComponent#isFillCenterVertical()
API: Added Install4jPropertyDescriptor#setPropertyChangeListener(...) to listen for property changes in the IDE. Changes on other properties are reflected after the listeners have been called.
API: com.install4j.api.FileOptions has a new constructor for delaying file installation on Windows if necessary
API: Added ReplacementMode I18N_ONLY for use in the AbstractBean#replaceVariables(...) methods
API: Added context Install4JPropertyDescriptor.CONTEXT_HTML for string properties that contain HTML
API: Added Install4JBeanInfo#setNoticePanel that lets you add a fixed panel at the top of the property editor
API: Added context FilePropertyDescriptor.CONTEXT_EXTERNAL_OR_INTERNAL for ExternalFile properties. When the file chooser is invoked, a dialog is shown that explains internal and external files.
API: Added com.install4j.api.launcher.ApplicationLauncher
API: Added new package com.install4j.api.update for auto-update functionality
API: Added Util.getAnnotatedStackTrace() and Util.printAnnotatedStackTrace() to add the bean origin of a stack trace
API: Added Util.showPath() to open a file manager for a certain file

Bugs fixed:

JRE bundles that only included the client VM did not work on server class Unix machines
After renaming a root in the distribution tree, the edit button was not enabled
Project was not properly synchronized in some cases when opening a new project
When editing a property and opening a new project, the save button could be disabled
Mac OS X: CFBundleGetInfoString in Info.plist did not contain the application version
XML actions: output files were not closed
XML actions: Existing DOCTYPE was not written
XML actions: output was not indented
Do not execute -Xshare:dump for JRockit JREs
Fixed NPE in unattended installer
Fixes file deletion problems on Linux
Fixed NPE when hitting Ctrl-C while actions are executed in console mode
"Show URL" action: URLs with anchors could not be opened
"Directory chooser" form component: Tree scrolled if user selected directories near the bottom of the tree
Fixed wrong file times for rollback
Catch more errors for preference store manipulations
"Check box" form components that were not initially selected were not correctly restored by a response file
Fixed proxy authentication problems on Linux
"Quit after screen" property was not honored by console and unattended installers
Console installers and unattended installers did not check the isHidden() and isHiddenForNext() methods of a screen
Installer variables were replaced directly when beans were loaded in the runtime, this lead to different behavior in the GUI and console installer
"Text area" form component: Editor for initial text was not multi-line.
"Append text to file" action: "Text" property was not multi-line.
context.goBackInHistory(...) now supports the parameter 0 to loop back to the current screen
Compiler variables in i18n messages were not replaced
Customizable screens: Installer variables in "Screen title" and "Screen subtitle" properties were not replaced
Customizable banner screen: Installer variables in "Info text" property were not replaced
Mac OS X: Add bundle identifier to prevent file associations to be connected to different install4j applications on newer OS X 10.4 versions
Linux: Exclude shared extensions from java.ext.dirs VM parameter for installer and uninstaller to prevent XML AbstractMethodError due to incompatible library versions
The file logger now saves files and directories as relative entries if the path starts with the installation directory. This allows the uninstaller to work for the installation directory even if the user moved the directory.
For multi-language installers, Util.getParentWindow() always returned the language selection dialog
Project Java versions lower that 1.3 crashed the build
Console handler for from screens did no correctly initialize form components. As a consequence, coupled form components were not correctly disabled or enabled in some situations
Chains of coupled form components are now supported, i.e. if a form component is disabled, all its coupled form components are disabled as well
String properties were always trimmed
Linux: Application registry on Linux did not always work with bundled JREs
Mac OS X: "Scan directory" class path entries were not dynamic
Console installer did not ask for proxy information if no direct internet connection is available
Accelerators for next and previous screen (ALT-Right and ALT-Left) did not respect whether the corresponding button was enabled and visible.
Using variable expressions of the type ${...} in Regexp properties that were not install4j variables produced an NPE at runtime
Selecting the "Installation directory" node in the definition of an installation component did not work
Installer variable sys.programFilesDir was only defined on Windows
Linux: When compiz is enabled, use MToolkit rather than the default XToolkit in order to avoid blank windows.
Temporary files created by Windows launchers are now deleted immediately after exit rather than on the next launch
Next and Previous buttons as well as all form components that take user input are now disabled when actions are executed
"Installation Directory" screen: Suggest user home if the standard installation directory cannot be written
Project export: scripts were not exported with proper indents and line breaks
The return code for Unix installers was always 0 even if the installer terminated with an error
API: JVMLocator.getJVMLocations() could return duplicate entries
A bundled JRE is now installed before other files in the distribution tree, so you can modify the bundled JRE with files in the distribution tree
"Install files" action: The AFTER_INSTALL_FILE event did not have the correct success value
"Installation components" screen: Component folders were always initially selected in console mode
"Directory selection" screen: console mode looped if "Only accept writable directories" property was selected