install4j releases

install4j Release 4.2.7

Thu, 11 Feb 2010 09:00:00 +0100

New features:

API: added com.install4j.api.Util#isWindows2008()
API: Added com.install4j.api.Util#is64BitWindows() to test whether the Windows is a 64-bit Windows regardless of the currently used JRE

Bugs fixed:

"Register Add/Remove item" action: The version was not displayed in the installation details of the software registry
"Register Add/Remove item" action: Entries from HKEY_CURRENT_USER which were created if an installer did not run with admin privileges were not removed by the uninstaller
"Run Executable" action: Do not replace path separators in environment variables
"Run executable" and "Execute launcher" actions: On Windows Vista or higher, launching executables in locations with non-ascii characters did not work anymore
Multi-language installers could hang after language selection under certain circumstances
Error dialog "Could not open message file" could not be displayed in headless modes
Under certain conditions, the navigation buttons in the installer were re-enabled before the next screen was shown
Mac OS X: Absolute paths for launcher redirection files were not supported
Mac OS X: Under certain conditions, a newly mounted installer could not be executed by the updater
Mac OS X: Fixed problem with non-ascii characters in description when using multiple file associations
Mac OS X launchers: environment variables with the syntax ${VARIABLENAME} were not replaced in redirection files and system properties
Windows launchers: fixed hanging processes in single instance mode when parent process exits immediately and many processes were started
Some splash screen image files were mistakenly reported as broken by the compiler

install4j Release 4.2.6

Mon, 14 Dec 2009 09:00:00 +0100

Bugs fixed:

Regression in 4.2.5: Validation in directory chooser validated content in text field instead of user selection
Regression in 4.2.5: Directory chooser was sometimes not opened if user clicked on "Browse"
Improved the error message that is displayed when the JVM cannot be started.
Launchers: Sometimes, the launcher icon was compiled even if the "Add icon to launcher" check box was not selected
Installer applications: The cross-platform icons were packaged even when "Customize icon" was deselected
"Run executable" action: Setting and clearing the arguments property value lead to the executable being called with a single zero-length argument
Custom icon of installer applications: The settings were not saved reliably
Installation components that were set to "not changeable" via the API were still displayed by the console installer
Installation component folders that contained only mandatory components were not shown with a disabled checkbox

install4j Release 4.2.5

Wed, 18 Nov 2009 09:00:00 +0100

New features:

"Load response file" action: Added an "excluded variables" property for variables in the response file that should be ignored.
"Create a file association" action: Added a "Role" property for Mac OS X to make the file association role configurable as "Viewer or "Editor"
"Bundled JRE" step of media wizards with dynamic JRE bundles: Added "Start download without user confirmation, if necessary" check box
Added an "Arguments" property to installer, uninstaller and custom installer applications that allows fixed arguments to be passed to the installer application
Directory chooser improvements: Rescan when directory is collapsed, new folder button at the bottom, context menu, dragging a file int the tree sets the current selection
File and directory chooser components: dragging files to the text field is now possible
Installation directory choosers and "customizable directory" screen: Added a "Manual entry allowed" property
"Directory selection" screen: Added "Validation script" property
All beans with directory choosers: The "validation script" property is now also executed in console mode and when the screen is validated, not only when for chooser button is used
Separate field for product name in windows version resource info step of the launcher wizard
Added VM parameter -Dinstall4j.suppressStdout=true to prevent status messages from being written to stdout in unattended mode
Added VM parameter -Dinstall4j.detailStdout=true to print installed file names to stdout in unattended mode
Added VM parameter -Dinstall4j.suppressUnattendedReboot=true to prevent a reboot in unattended mode

Bugs fixed:

"Password field" form component: do not trim leading and trailing spaces of passwords
Mac OS X install4j ant task did not work with Java 1.6
"Add desktop link" action: The action will now try to append .exe on windows if the destination file does not exist
Changed desktop file in order to prevent the "untrusted application" message on GNOME
Installation directory selectors: In console mode, it was was not checked correctly if the selected directory is suitable
"Installation type" screen: Variable sys.installationTypeId was not set in console mode
Fixed execution of downloaded update installers with bundled JREs on Unix
The generated file classes.jsa of a bundled JRE was not removed when the installer was canceled
Fixed compile exception for launchers in excluded file sets
Mac OS X: The date in the DMG file was wrong
If "Insert after selection" was selected in a bean registry dialog, some beans were inserted in a wrong position
Compiler variables could not be used when overriding the message key UninstallerMenuEntry
Fixed backspace handling in console mode when using Putty 0.5 and AIX
"," is not a bad character for program group names
The previous JRE was not restored on rollback
API: com.install4j.api.SystemInfo.getPhysicalMemory() did not work for Linux 2.4 kernels

install4j Release 4.2.4

Wed, 16 Sep 2009 09:00:00 +0200

New features:

Launchers: Added option in redirection step of the launcher wizard to append output to existing redirection files
Added a "Console handler" form component
Added a "Console screen change handler" property to all installer applications. With this script it is possible to insert a header or custom messages at the beginning of each screen in console mode.
Mac OS X media types: Added a "64-bit settings" step that allows you to force the use of a 32-bit JRE. This is necessary on Mac OS X if your application loads 32-bit libraries.
All screens and form components with a directory chooser: Added a "Allow new folder creation" property. If selected, a button for creating new folders will be displayed in the chooser dialog.
"Replace text in XML files", "Modify a text file" and "Modify a text file with regular expressions" actions: Added "Log replacement text" property that can be disabled for security reasons
"File chooser" and "Directory chooser" form components: Support leading ~ for home directory
Windows service launchers: Added the option non-interactive after /install to register services that should not allowed to interact with the desktop.
Custom localization files can now contain references to compiler variables, installer variables and other i18n keys
Added the capability for extensions to contribute localization files (see the "Extensions" help topic)
Added an "Arguments" property to installer, uninstaller and custom installer applications that allows fixed arguments to be passed to the installer application
API: Added com.install4j.api.windows.WinRegistry#getValueNames
API: Added version of com.install4j.api.windows.WinFileSystem#createStartMenuEntry that allows arguments
API: Added com.install4j.Util#isAix
API: Added com.install4j.api.InstallationComponentSetup#setChangeable(boolean) and isChangeable. With these methods the user can be prevented from changing the selection state of an installation component.

Bugs fixed:

Control characters at the beginning of variables that are read from the command line were not removed
Fixed a problem when uninstalling file associations for well known file types
A listener registered with com.install4j.api.launcher.StartupNotification was not called reliably for a rapid succession of invocations
"Key value pair" form component: Missing line break in console mode
"File chooser" form component: Leading label was not baseline-aligned
"File chooser" and "Directory chooser" form components: The "Validation script" property was not passed a "file" argument
"File chooser" form component: If initial directory is empty, the file chooser opened in the temporary directory, this has been changed to the directory where the installer media file is located
"Show URL" action: On Unix, the browser was sometimes not shown if the action was added to the "Finish" screen
"Register Add/Remove item" action: The keys InstallLocation, VersionMajor and VersionMinor for the uninstaller entry were not set
"Execute launcher" action: The action failed on Mac OS X with Java 6 update 4 when "Restart as root" was selected for a preceding "Require admin user" action
Fixed starting of elevated launchers on Windows 7
Added a workaround for an undefined TMP environment variable
"Single radio button" and "Check box" form components: Selection scripts were not executed in console mode
"Download file" action: Status label could wrap for long file names and damage the screen layout
A log file was left in the temporary directory after installation
Formatted text field components did not work correctly in console mode
install4j version and build number are now included in the installation log file
"Installation type" screen: Component selection could be wrong due to component dependencies
The value in a focused form component with formatted text was sometimes not transferred to the bound installer variable when an input validation expression was present
Multi-line label form components did not wrap in text in console mode
Response files could not have a UTF-8 byte order mark
The input validation expression of invisible or disabled text components was always executed when the form was validated
Visibility expressions were not executed in unattended mode
Canceling a console installer could print an exception
Custom installer applications on Mac OS X could not be executed before the "Install files" action had run
API: com.install4j.api.windows.WinFileSystem#createStartMenuEntry was not rolled back

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 writable
"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