install4j 5.1.4

v5.1.3 [09-28-12]

  New features:

• Generated executables now pass Windows 8 certification
• Mac OS X launcher wizard: On the "Executable info->Mac OS X options" step, you can specify an entitlements file for code signing (relevant for App Store deployments)
• Mac OS X: Installer applications have a "Mac OS X Entitlements file" property
• Mac OS X media file wizard: On the "Installer options" step, you can enable signing of all installed launchers (relevant for using certain OS features such as iCloud storage)
• Mac OS X: Support VM passthrough parameter (prefixed with "-J") like on Windows and Linux/Unix (OpenJDK only)
• Mac OS X: Support -include-options directive in VM parameters (OpenJDK only)
• Mac OS X: Also read .vmoptions file next to the application bundle (OpenJDK only)
• Mac OS X: install4j IDE now works in full screen mode
• "Run executable or batch file" action: Added a "Wait for output streams" property below the "Wait for termination" property which can be deselected so that the action does not wait for child processes to terminate
• Support for non-ASCII path names in tar files

• Added Util.isWindows8()
• JVMSelector now finds Oracle JRE on Mac OS X

• "Installation type" screen: If the IDs of installation components were customized, the initial installation type could not by set by a response file
• "Directory selection" screen: Fixed NPE if the initial directory was empty
• Floating licenses: Setting the license server on the command line with "install4jc --license FLOAT:server" was not documented, added the new options --windows-edition and --multi-platform-edition to change the desired edition
• Rollback of file installation was always executed at the end. This could lead to wrong results in combination with "Delete files and directories" action.
• "Download file" action: Deselecting "Show progress" did not completely disable progress messages
• Actions that were executed through a link to a single action were never elevated
• Proxy dialog was sometimes not shown when downloading a JRE in the install4j IDE
• Setting -DproxyAuthPassword did not work, the proxy dialog was always shown if a password was required
• The selection of a JDK for the code editor on the General settings->Java version tab was not saved in the project (regression in 5.0)
• Build hung in command line mode when wrong keystore password for code signing was entered
• Linux: Localized desktop directories were not supported
• Custom JRE bundles: JavaFX JAR file was not unpacked
• Fixed a race condition with the install4j splash screen
• Windows code signing: Also handle SPC files in PEM format
• Mac OS X code signing: Allow non Apple certificates
• Mac OS X: install4jc did not work when Java 7 was set as the default
• Mac OS X: Java 7 could not be used for code editor
• Mac OS X: Avoid duplicate classpath entries
• Mac OS X: An installed Oracle JRE was not found
• Mac OS X: -include-options directive was not supported in .vmoptions files (OpenJDK only)
• Mac OS X: environment variables were not expanded in .vmoptions file (OpenJDK only)
• Mac OS X: File encoding was wrong when OpenJDK was used

v5.1.2 [07-31-12]

  New features:

• Project compilation now produces a file "output.txt" that list all generated media files, their IDs, display names and platform types
• "File chooser" and "Directory chooser" form components: Added a "Initial browser directory" property

• Install4JPropertyDescriptor.CONTEXT_NO_INSTALLER_VARIABLES now also works for properties of type java.io.File
• In addition to .utf8 files, .properties files are now supported as extension localization files

• context.getInstallationComponents() could not be called from an elevated action (regression in 5.1)
• Moving back and forth through through screen groups could cause the installer to fail (regression in 5.1)
• "Install files" action: Fixed exception when "delay if necessary" was used for elevated install files action (regression in 5.1)
• "Hyperlink action label" action: variables in the hyperlink text were not replaced in console mode
• "Hyperlink action label" form component: Show label text in console mode if defined
• "Install files" action: If "Show file names" is deselected, the unpacking progress for packed JAR files was still shown which did not make any sense to the user
• "Leading label" form component: If only an icon and no text was configured, the icon was not shown
• "Start a service" action on Mac OS X: Removed printing of an uncritical exception
• "Single radio button" form component: In console mode, the installer could hang under some circumstances
• Mac OS X code signing: Automatically add Apple certificates if .p12 file contains no chain. The "certificate export" functionality is no longer necessary and has been removed.
• Mac OS X code signing: Fail during build if an unsuitable certificate is provided
• Mac OS X: com.install4j.api.JVMSelector did not return the real home directory of the JRE bundle
• Mac OS X: Mark all launchers as high resolution capable for retina displays
• Linux/Unix: Fixed problem where file modes could not be changed during update installations
• Linux/Unix: com.install4j.api.unix.UnixFileSystem.setMode did not work under some circumstances
• Updaters would throw an NPE in the "Finish" step if the downloaded media file was an archive
• Custom installer applications: external files (such as icons) in were not loaded
• Custom installer applications: An empty working directory lead to an error during build
• Progress operations would not work if a screen with a progress interface was executed through a link
• Compiler variables could not be used in custom localization files
• Linking to screen groups in the same installer application was broken
• In console mode, when cancelling an installer, the subsequent prompt on the terminal could be indented
• Using links in custom installer applications that were contributed from merged projects did not work
• The ID of the uninstaller launcher at runtime was not "uninstaller", but a generated and non-configurable ID
• Do not add custom code jar files to the class path more than once in the installer
• Cached proxy information was never used if the auto-detected browser config was wrong
• Unbalanced quotes for arguments were not handled correctly by launchers

v5.1.1 [07-09-12]

  New features:

• Mac OS X launchers: On the Executable info->Mac OS X options step of the launcher wizard, you can now specify a custom bundle identifier
• "Read value from XML file" action: Added a "Variable name for node" property to save the org.w3c.dom.Node value of the match
• Support for compiler variables in pre-defined installer variables of type string and string array

• Several command line options were broken (regression in 5.1)
• Javadoc formatting of the API documentation was broken (regression in 5.1)
• Generated installers did not work on OS X 10.5 (regression in 5.1)
• Windows code signing corrupted various 64-bit executables
• Run executable action could not be elevated
• When setting a wizard index for a particular screen, it could not be changed again when showing the screen for a second time
• The installer variable "sys.installationDir" was not written to the response file if the "Installation location" screen was not present in the project

v5.0.11 [01-25-12]

  API changes:

• Fixed NPE when an error message was show in com.install4j.launcher.ApplicationLauncher
• Return null for special folder API when used on non-windows platforms instead of throwing an exception

• Fixed locale regressions in 5.0.10
• Distribution file choosers were not shown if the install4j IDE was run with Java 7
• "File version" property for uninstaller and and custom installer applications had no effect, the product version was always used for the Windows version resource
• Unix installers were broken on some systems
• Windows: If the user was changed during UAC, the program groups were not created for the original user
• Installation directory chooser form component: Disabling the form component did not disable the chooser button

v5.0.10 [12-12-11]

  New features:

• Added progress feedback for unpacking JAR files that were packed with Pack200 as a percentage number after the file name in the status line
• Windows: The auto-detected language is now the "Display language" setting defined in the "Region and Language" Windows control panel, independently of the used JRE
• Support Java 7 for the install4j IDE and the command line compiler (launchers and installers have already supported Java 7 before)

• Added ProgressInterface#setSecondaryPercentCompleted to add progress feedback for secondary tasks in the status line
• UpdateChecker.getUpdateDescriptor threw an NPE instead of an IOException if the connection could not be made to the server

• "Directory chooser" and "File chooser" form components: The validation script was not executed when the user clicked on the Next button, so manual changes were not validated
• "Installation type" screen: If custom IDs were defined for the installation types, the installer variable "sys.installationTypeId" was still set to the numeric ID of the selected installation type in console mode
• "Write text to a file" action: Line separators of the runtime platform were not always used in the written file
• "Installation directory chooser" component: A duplicate existing directory warning was displayed in console mode at the end of the form
• "Installation directory chooser" form component: Validation was run even if the component was not visible or not enabled
• "Download and install component" action: The action could only be added once to a project
• All "Spinner" and "Text field with date format" form components: Value initialization was broken for response files
• "Add Windows file rights" and "Add access rights for a key in the Windows registry" actions: Installer variables were not replaced in the "SID or account name" property
• "Display progress" screen: Installer variables in the "Initial status message" property were evaluated at startup and not when the screen was activated
• "Hyperlink URL label" form component: Installer variables in the displayed URL were nor replaced in console mode
• "Add a desktop link" action: The specified icon had no effect for links to a .url file
• ant task: If the "buildids" parameter was specified with an empty value, no media files were built
• Creating a file association could throw an exception
• A hidden installation component that was initially selected was not installed in console mode
• Surrounding white space in answers to multiple choice questions in console mode was not ignored
• Generated service launchers were not compatible under Red Hat Linux
• Mac OS X: Packed custom code jars that are not in the distribution tree were not used for the uninstaller
• Updater applications did not work if they were launched in the same process
• Launchers on Mac OS X and Linux: Native library path entries containing environment variables to an absolute path did not work
• The update descriptor file could contain duplicate elements for the principal language if it was also added as an additional language
• Mac OS X: A preference store bug in Mac OS X 10.7 broke the detection of previous installations
• Some operations in SWT applications could be slow due an application manifest entry
• Automatic launcher integration did not work in MAC OS X single bundle media files
• Single instance mode for launchers was broken if there were spaces in the name of the executable
• Updaters that were started by launcher integration in the same process at startup did not switch to the native look and feel
• Language auto-detection did not work in unattended mode
• Fixed a Debian package warning
• Linux/Unix installers: If the environment variable GREP_OPTIONS was defined, the installer could break
• Closing the language selection dialog with the window close button could leave the installer hanging
• "Bundled JRE" step in the media wizard: A change in the 32-bit/64-bit selection in the previous step was not considered for the choice of bundled JREs

v5.0.9 [07-13-11]

  New features:

• Installer applications: Added a "Progress interface creation script" property to customize the display of progress information for unattended installations
• Installer: Added a "Replacement script for language code" property. This can be used to change the auto-detected language or to implement custom auto-detection of the language that should be used.
• Installer applications: Added a "Help customizer" for modifying the displayed help on the available command line arguments
• "Set a variable" action: Added a "Register for response file" property
• Added a "Hide help button" option on the "Description" tab of the installation component property sheet
• Added a launcher variable "sys.tempDir"
• Added a compiler variable "sys.time"

• Added com.install4j.api.context.UnattendedProgressInterface and com.install4j.api.context.DefaultUnattendedProgressInterface for the "Progress interface creation script" property of installer applications
• Added Context#getVersion() to get the version of the installed application
• Added Context#getMediaFileId() to get the media file ID of the installer
• Added Context#getExtraCommandLineArguments() to get command line arguments that were not processed by the installer
• Added FormEnvironment#reinitializeFormComponents() to re-run the initialization of all form components
• Variables#getInstallerVariable(String) and Variables.getInstallerVariables() do not throw IOException anymore. If the automatically created response file cannot be read (as is the case for archives), system variables are still available from these methods
• Calling UpdateChecker.getUpdateDescriptor with ApplicationDisplayMode.GUI would throw an NPE if the proxy dialog had to be displayed
• Script properties could not have array return types

• Prevent PCA mitigation ("This program might not have installed correctly”) for Windows 7
• Fixed exception when running an installer with certain layouts with Java 1.5
• "Help text" tool tip labels in customizable forms were focusable
• Text form components on tabbed panes: If validation failed with an error message, the parent tab of the text form component was not shown
• Encoding in displayed HTML files was not detected correctly
• "HTML display" form component and screens showing HTML text: For direct entry, installer variables were not replaced in the HTML
• "Installation components" screen: Fixed flickering when toggling the help buttons in the tree
• "Installation components" screen: Only show tree lines if the the component tree has component folders
• "Create program group" action: On Unix, the default value of the "Directory for links" property did not use the user input from the "Create program group" screen
• For a wizard index that was defined in the IDE, installer variables were not replaced in the keys and step names
• Fixed NPE when writing a response file with a string array variable value containing a null value in one of the array elements
• Util.showOptionDialog did not show default value in console mode and numeric keys were displayed. This was inconsistent with questions from form components. Keys are now taken from the first letters of the supplied options and can be set explicitly by prefixing the letters with '&'.
• Links to screens or actions in merged projects could fail at runtime under some circumstances
• For certain network errors, downloads would not time out and hang the installer
• If no initial text was set for the status and version lines in the splash screen configuration of a launcher, subsequent updates via the API has no effect on Unix and Mac OS X
• Generated .vmoptions files were not preserved by the "Uninstall previous installation" action
• Installer variables could no longer be used when overriding system messages (regression in 5.0.8)
• System installer variables were not available for archives
• PDF screen and actions did not work anymore
• Using installer variables with numeric values as arguments to i18n keys in expressions like ${i18n:myMessage(${installer:myNumericValue})} did not work
• For launchers in archives, installer variables in system properties and arguments were not replaced with "null" if no response file was available. This was inconsistent with the behavior of launchers in regular installers
• The error output of install4j command line tools was redirected to a file and not displayed on the terminal (regression in 5.0.8)
• If an error occurred during script compilations, lots of warnings regarding serialVersionUIDs were printed as well (regression in 5.0.8).
• Media wizard: In the "Exclude components" screen, if a folder was excluded, the component tree was not displayed the next time that the project was loaded
• Media wizard: When pack200 compression was activated, file exclusions did not work for JAR files that were also used in custom code
• The "createbundle" command line tool did not work in headless mode
• File exclusions for directory entries in the distribution tree were not saved when "Add to subdirectory" was selected for the entry
• Windows registry: Strings stored without null termination were not read correctly
• Windows service shutdown did not work correctly when user code redirected System.in
• Windows user creation failed under certain circumstances
• Mac OS X: An unnecessary test file remained when the installer process was elevated
• Mac OS X: It was not possible to use very long installer names
• Mac OS X: No text field was shown for certain file chooser dialogs in the install4j IDE
• Unix: Installers and launchers did not work if the $HOME directory was not writable
• Unix: Several actions would fail to operate on files whose names contained a dollar sign

v5.0.8 [04-14-11]

  New features:

• "Install files" action and "Download and install component" actions: In console mode, file names are now shown on the same line to avoid a long scrolling list of file names
• In console mode, HTML tags are now removed in all text output. Multi-line messages use an HTML to plain text conversion that conserves line breaks, lists and similar layout tags.
• "Create program group" action: Windows program group entries now have an additional "Run as administrator" option

• ProgressInterface#setDetailMessage: In console mode, repeated invocation of this method overwrites the current line. This prevents a long scrolling list of temporary information.
• Added Screen#hasDefaultButtons() for hiding the navigation bar at the bottom of the screen
• Context#isUpdateInstallation was not updated when the installation directory was changed by the "Installation location" screen in console mode
• Added WinFileSystem#createStartMenuEntry method with an additional runAsAdministrator parameter

• Regression in 5.0.7: File selection for installation components was not saved
• Regression in 5.0.7: Using installer variables in custom localization files did not work as expected anymore, all variables were replaced at startup instead of at the time of usage
• "Create a file association" action: On Mac OS X 10.6, the action did not have any effect until the next reboot
• In console mode, "Downloading ..." was displayed even if no component data files were actually downloaded
• "Multi-line HTML label" form component: In console mode, blank lines were printed before and after the text
• "Fix line feeds" action: The file property was lost when reading a project saved by install4j 4.x
• "Uninstall previous installation" action: An already installed JRE bundle was deleted, which could cause problems
• It was not possible to insert i18n messages which contained installer or compiler variables by using the variable selector
• Unix: Unwanted logging output of the java.util.preferences subsystem was not switched off early enough
• Unix: Installing directly into the home directory did not work. This could be the case if a dedicated user was created whose home directory was set to the installation directory.
• Windows launchers: Error messages about invalid environment variables in the search sequence contained an unresolved variable
• "Fix line feeds" action: In console mode, exceptions were printed if a file or directory did not exist
• "Directory selector" and "File selector" components: In console mode, if the bound variable was defined before the screen was shown, the selector did not show the defined value as the default value
• Updater templates did not force unattended update installers to use the current installation directory which could be a problem if multiple installations of the same product existed
• Max OS X: The code editor dialog would not appear the first time a script was edited

v5.0.7 [03-22-11]

  New features:

• Windows installer: Language auto-detection is now also implemented in the native initial progress dialog. If the user language is configured for the installer, it will be used with a fallback to the principal language.
• Windows launchers: Make executable name available for JVM discovery, for example in VisualVM
• Support for .properties files in the editor for custom localization files (ISO-8859-1 encoding and java.util.Properties-style escaping)
• Improved version comparison for auto-updates. Sequences like 2.0 beta 2 -> 2.0 rc 1 -> 2.0 are now compared correctly
• "Uninstall previous" action: The log file of the uninstaller is now written to .install4j/uninstallPrevious.log

• Added com.install4j.api.screens.Screen#hasDefaultInsets which makes it possible to develop custom screens that take up all available space
• com.install4j.api.context.Context#runElevated(...) and #runUnelevated(...) were broken
• UpdateChecker#getUpdateDescriptor did not ask for proxy information if a connection was refused
• AbstractBean#replaceVariables methods did not replace installer and compiler variables when called during the initialization phase of a bean
• InstallerContext.isUpdateInstallation() returned true for any installation if it was called for the first time after the "Install Files" action had already run

• "Request privileges" action on Mac OS X: Pack200 compression did not work correctly if the main installation process was elevated
• "Vertical spacer" form component: No space was added in console mode
• "Welcome" screen: Form components with a horizontal size that exceeded the available space broke the layout
• "Create program group" action: Menu integration on Linux/Unix was not always removed during uninstallation
• "Windows user selector" form component: Any SIDs already contained in the bound variable were not displayed in the user selector and discarded on "Next". This prevented the pre-definition of SIDs with response files.
• "Run executable or batch file action": Redirection files were not closed immediately after a successful execution
• "Welcome" screen: Form components were not displayed in console mode
• "Finish" screen: No message was printed in console mode
• "Hyperlink label" form component: Nothing was printed in console mode
• "Create program group" action: The "Display icon" property of URL links did not have any effect in modern Windows versions
• Windows: Fixed UnsatisfiedLinkError during some installations
• Windows launchers: In the fixed VM parameters for launchers and installers, a "
  " was replaced with a newline character
• Windows: When running processes were detected in console mode, an exception was thrown
• Windows: When starting an installer with the -h argument, a corruption warning was shown for the next start
• Windows services: Do not report an error for service uninstallation when the service is already marked for deletion
• Windows services: Do not report an error when stopping a non-active service
• Windows services: The /status command line argument did not work under some circumstances
• Mac OS X daemons: The service actions could fail if an 3rd part plist file with an error was present in /Library/LaunchDaemons
• Mac OS X archives: Command line executables did not have the executable flag
• Mac OS X: The elevation helper processes showed an extra dock icon when INSTALL4J_ARGUMENTS was defined for a GUI installer
• Linux DEB files: Empty dependencies could cause problems with repositories
• Some classes from the install4j API could not be used in scripts, because the compiler did not find them
• Hosts name exceptions in browser proxy configuration were not respected for downloads in install4j
• Proxy information for downloads was not always applied immediately when changed in the browser
• Proxy information in the browser was used even if the proxy was disabled in the browser
• Proxy dialog was not shown in unattended mode with progress dialog
• The variable "sys.programGroupDir" was not available if the "Create program group" screen was not displayed
• Excluding file sets in the media wizard from merged projects caused an NPE in installer
• vmoptions files: "-include-options" command did not work correctly with relative files
• If the "Do not delete temporary directory" build option was selected, generated script sources were still deleted
• At runtime, missing keys in custom localization files did not fall back to the principal language
• Sometimes the installer unnecessarily asked the user about replacing icon files on Linux/Unix
• Prevent multiple error dialogs if auto-saving does not succeed
• Quick search in list of bound installer variables did not work
• HTML tags were shown for some messages in console mode
• Some file modification actions printed exceptions in console mode
• Hiding an installation component had no effect in console mode
• The language selection in console mode was not presented in the user language, but always in the principal language
• Non-error messages were printed to stderr instead of stdout in unattended mode

v5.0.6 [12-22-10]

  New features:

• "Install a service" action: Added a "Windows arguments" property for arguments that are passed to the main class
• "Write text to a file" action: Added a "Log text" property for preventing the replaced text to be written to the installation.log file
• "Run executable or batch file" action: In the redirection properties, /dev/stdout, /dev/stderr and /dev/stdin connect to the default streams of the installer application
• "Check for running processes on Windows" action: For relative files in the "Additional executables" property, only the names of the executables are used for comparison. This enables checking for executables with an unknown location.
• Installer applications: Added a "Disable console mode on Windows" property
• Use a better file choose dialog in the install4j IDE on Mac OS X (from the Quaqua Look and Feel)

• Added Context#unregisterResponseFileVariable(String) to reverse the effect of Context#registerResponseFileVariable(String)
• Added WinUser#getUserName(String sid) to get the unqualified user name
• Added Win32UserInfo#getUserProfileDirectory(String sid, String password)
• Added WinFileSystem#getDriveType() to check for removable drives

• "Run executable or batch file" action: On Mac OS X, the "Wait for termination" property had no effect if an application bundle was started
• "Run executable or batch file" action: On Windows, use less quotes for arguments to avoid issues with programs that do not expect quoted arguments
• "Run executable or batch file" action: If the .exe extension was missing, the executable was not launched on Windows under certain circumstances
• "Run executable or batch file" action: In the installation log file, the values of the redirection files properties were reported without variable replacements
• "Run executable or batch file" action: If a redirection file was set to an installer variable, and that variable contained the empty string, the execution failed
• "Run executable or batch file" action: On Windows, AutoRun commands defined in the registry were not ignored
• "Request privileges" action: On Windows, the action did not work with normal users when UAC was disabled
• "Request privileges" action: On Mac OS X, external media files and elevation of the main process did not work together
• "Add VM options" action: On Mac OS X, the action would fail under certain circumstances
• "Install Files" action: Files were extracted before the user was asked whether an existing file should be overwritten. For large files, this would waste time for the user.
• "Uninstall Files" action: The file classes.jsa of a bundled JRE was not deleted for server VMs
• "Uninstall files" action: In certain cases, shared files were not uninstalled as expected
• "Read a key from the Java preference store" action: The property "Preference root" could not be changed in the install4j IDE
• "Installation components" screen: If multiple hidden installation components were on the same level in the component tree, only the first one was actually hidden.
• "Delete files and directories" action: The action resulted in an error if a file did not exist, which conflicts with the behavior in install4j 4.x. Now the action returns with success even if the file that is to be deleted could not be found.
• "Set a variable" action: Exceptions were not reported in the installation.log file
• Add-on installers installed their own install4j runtime, which could lead to broken uninstallers if runtime library shrinking was enabled
• Regression in 5.0.5: project reports were not opened immediately in browser
• It was not possible to exclude the uninstaller in the "Customize project defaults->Exclude installer elements" step of the media wizard
• Fixed a FileNotFoundException when JAR files were used in the custom code and multiple media files were built
• Single class custom code entries did not work when compiling on Mac OS X
• Windows: The silent installer did not automatically download a dynamic JRE bundle when the direct downloading option was selected on the "Bundled JRE" step of the media wizard
• The "Uninstallation failure" screen was always shown for the installation dir on Mac OS X
• Windows: When msvcrt71.dll was not present in windowssystem32, a bundled jre was used, and a launcher was started after installation, the installer always asked for a reboot
• The "Global exclude" pattern under Files->File Options was not saved to the project file
• When changing between different project windows, the file chooser could show the wrong distribution tree under some circumstances
• Fixed a rare string corruption problems with installer settings that were saved to the Windows registry
• Public JREs on HP-UX were not found
• Using links in the same installer application led to ClassCastExceptions at runtime under certain circumstances
• The "preserve" option of the command line compiler was not available on the ant task
• If a download URL was specified on the "Bundled JRE" step of the media wizard, it was used even if the "Don't bundle" a JRE option was selected
• The -wait command line option did not work with unattended mode on Windows. Unattended updaters were mainly affected by this bug.
• Form components: The tool tip help label from the "Help text" property was not shown under some circumstances
• Unix launchers: Using installer variables for redirection files broke the launcher script
• Choosing the "According to update schedule registry" mode on the "Launcher integration" tab of installer applications did not work
• Windows: Services were uninstalled when the service path was changed during an update
• A rollback could leave the file .install4j
  esponse.varfile in the installation directory
• Unix installers did not work with some IBM JREs
• Partially downloaded files were not deleted
• Mac OS X: Pack200 compression was not applied for JAR files in custom code
• Mac OS X: Console launchers could only find the default JRE
• Compiler variables could not be overridden for merged projects from the command line or the ant task
• AIX: Exceptions were printed when an installer was executed
• Mac OS X: The system menu was changed for in-process execution of custom installer applications
• Do not write the default chkconfig info to unix daemon scripts if the custom script for the launcher already contains a chkconfig header

v5.0.5 [09-30-10]

  New features:

• Installer applications: Added new execution mode "Unattended mode with progress dialog" and child property "Title for progress dialog". This is the same functionality that is available from the command line with the -splash [title] arguments.
• System installer variables such as "sys.userHome" are now available for launchers, e.g. in redirection file names and the in com.install4j.api.launcher.Variables class
• The build options in the Build step of the IDE are now persistent

• Under some circumstances, the proxy dialog was not displayed and an exception was thrown instead
• Installer variables could not be used for redirection files of generated launchers
• Under some circumstances, privilege elevation did not work for normal users on Mac OS X
• Installer variables were not resolved when executing a launcher from the installer, because the response file was not yet written
• Update detection did not work for Mac OS X single bundle installers
• Custom code entries with spaces in the path could not be found by script compiler
• If -Dinstall4j.keepLog=true was passed to the installer, the temporary log file was not preserved if the installation was successful
• Windows launchers: Service arguments embedded in the registered binary path did not work correctly
• unpack200 failed on some Windows machines
• "Run executable" and "Execute launcher" actions: On Mac OS X, application bundles were not executed with /usr/bin/open, so it was possible to start them multiple times
• The command line compiler hung on Mac OS X when a vmoptions file without a trailing line feed was processed
• Fixed NPE with launcher integration
• Generated vmoptions files were not included when launcher was selected directly in the component selection
• Custom code jars were not copied to the final destination when selected directly in the component selection
• -Dinstall4j.debug=true was not set in debug scripts, so stack traces were not printed to stderr
• installer variables: In properties with array values (like the arguments of a "Run executable" action), empty array values resulting from empty installer variables were not pruned from the resulting array
• Unix launchers: Installer variables in fixed VM parameters and arguments were always replaced with empty strings
• If there was a fatal error while writing the update descriptor, the build process in the install4j IDE would hang
• Unix installers: Since JRE 1.6.0_17, the workaround for hiding annoying messages from the java.util.prefs subsystem did not work anymore

v5.0.4 [09-13-10]

  Bugs fixed:

• Custom icon for the installer was not used for the wizard window (regression in 5.0.3)
• Clicking on the "Finish button" in install4j IDE wizards closed the wizard immediately (regression in 5.0.3)
• "Create a ZIP file" action: Installer variables were not replaced in the "ZIP file" property
• Definitions in a response file that was specified with the -varfile command line option were overriden by predefined installer variables
• Fixed a deadlock for Windows launchers
• Fixed deadlock while saving a project
• Mac OS X: The content of a vmoptions file specified in the launcher wizard was not added to the static VM parameters for command line and service launchers
• Windows: Invisible windows could have the name "Default IME" or "theAwtToolkitWindow" which was displayed by the check for running processes. Now, the file name is used in these cases.
• Auto-saving of a project file was not stopped after a frame was closed
• Text form components: If "Prevent empty user input" was selected, disabled components produced a warning message, too
• Transparency in customizable banner form screens was sometimes incorrect for the classic Windows Look and Feel
• It was not possible to use ampersand characters in custom message files
• Could not pass "-e" to unix scripts when VM pass-through parameters were enabled
• Starting services with "For Auto start installations only" selected did not work for services generated by install4j
• Custom installer applications in archives did not work when runtime shrinking was enabled
• Using compiler variables for fixed installer arguments or VN parameters did not work when debug installers were generated

v5.0.3 [08-01-10]

New features:

• "Welcome" screen: The screen is now a container for form components
• Media file wizards of installers: Added a project customization step to statically include selected installation components that have been marked as downloadable for the whole project
• When invoking unattended installers with the "-splash" options, there is now a cancel button.
• Added a "Change cancel button state" action
• "Run executable" action: Added a "Variable name for return code" property (nested property of "Wait for termination"), so you can use the return value later on.
• Added an installer variable sys.workingDir

• Added com.install4j.api.context.InstallationComponentSetup#isDownloaded()

v5.0.2 [07-17-10]

New features:

• Windows: Add a window entry to the task bar if a dialog box is shown while the main installer window is not visible

• Pack200 compression was not applied
• Display output of code signing post processor in order to help with debugging configuration problems
• Installer applications: Variables in the "Custom watermark text property" were not replaced
• The check for update action of the install4j IDE would crash under certain circumstances
• Including certain JAR files in custom code lead to a "No disk space left" error in the installer
• "Create program group" screen: Installer variables in the "Program group name" and "Directory for links" properties were not replaced
• "Copy files and directories" and "Move files and directories" action: Single file to file operations did not work as in 4.x.

v5.0.1 [07-01-10]

New features:

• Improved the preview dialog for configurable forms to make it more like the actual screen at runtime
• Allow a * placeholder in classpath archive entries to support frequently changing version numbers of JAR files like in maven projects

• API: added methods in com.install4j.api.windows.WinRegistry to access the 32-bit and 64-bit registry views on 64-bit systems

v5.0 [06-18-10]

New features:

• Improved elevation of privileges on Windows and Mac OS X:
• The new "Request privileges" action replaces the "Require admin user" action. It can elevate the main installation process or create a helper process with full privileges and works on Windows and Mac OS X.
• "Run executable or batch file" action: The "Execution account" property allows you to run the executable as the original user or as an admin user
• Service actions and actions that add rights on Windows will be executed in the helper process with full privileges if the "Request privileges" action was configured accordingly
• The "Show URL" action, the "Show file" action and the "Execute launcher" action will be executed as the original user if the "Request privileges" action has elevated the main installation process
• "Install files" action: Use original user rights when parent directory of an installed file belongs to the original user. This is relevant if the installer has been elevated with a different user account.
• Major improvements for installer variables, compiler variables and i18n messages:
• The variable selection dialog was redesigned. It supports filtering and shows default values and descriptions for all variables
• Many new system variables were added
• Compiler variables can now be organized in a tree and have descriptions that are shown in the variable selector
• Installer variables can be pre-defined similar to compiler variables
• When inserting variables, the correct expression is inserted for text fields, scripts and variable name properties
• Installer variables that are bound to beans are detected and displayed in the variable selector
• Bindings of installer variables are detected and displayed with back traces for each installer application
• Custom localization files can now be created and edited in the install4j IDE, an action for overriding system messages is available in the editor.
• More flexible and usable IDs:
• All elements that have IDs can now be assigned custom IDs. The automatically assigned IDs continue to be valid.
• The script editor now offers a dialog that lets you choose an ID by listing all available elements with IDs
• Improvements for actions that operate on files:
• Actions that operate on files now accept multiple files where appropriate
• Actions that operate on multiple files now have "File filter" and "Directory filter" properties to control file processing with scripts
• Launcher integration for custom installer applications:
• A launcher integration tab has been added to custom installer applications where you can configure automatic invocations when launchers are executed. This is particularly useful for updaters.
• On the "launcher integration tab", an integration wizard for calling custom installer applications from Java code is available
• Improvements for the auto-update functionality:
• All features of the update descriptor (updates.xml) are now exposed on the new Installer->Auto-Update Options tab
• Some features of the update descriptor can be set on a per-media file basis in the Customize project defaults->Auto update options step of the media wizard
• Updaters templates now reference the URL for updates.xml with the new compiler variable sys.updatesUrl
• Comments in the update descriptor are now localizable
• Extensive support for Windows users accounts:
• Added a "Windows user selector" form component that also has the ability to create new users
• "Install a service" action: The "Account" property has an "Other" option that lets you set a specific user to run the service
• "Add access rights for a key in the Windows registry" and "Add Windows file rights" actions: The "Trustee" property has an "SID or Account name" option that lets you set a specific user
• Improvements for service actions:
• Service actions now support service executables that were not generated by install4j. If you set the "Service" property to "Other executable", an executable and a service name can be configured.
• Service options can now be configured for each "Install service" action instead of the previous per-launcher configuration in the launcher wizard
• "Install service" action: Added a "Windows priority" property
• "Install service" action: Added an "Account" property
• "Install service" action: Added a "Keep current account" property to preserve account changes by the user that were made manually after the installation
• "Install service" action: Added a "Restart on failure" property
• "Install service" action: Added an "Interactive" property
• "Install service" action: Added a "Mac OS X identifier" property
• Services on Mac OS X now use the more modern "launchd" subsystem
• Improved handling of custom code and resources:
• Custom code: The single user JAR file will only be created for directory and single class file entries. JAR files and resource files will not be packed into the single user JAR file anymore, they will be extracted to the .install4j/user directory. This directory is available from the sys.resourceDir installer variable.
• Custom code will never be packaged twice. If the same JAR file should be installed, it will be moved from the .install4j/user directory where the custom code has been initially extracted.
• Corruption detection and checksum verification for installers and downloaded components:
• Improved corruption detection and error messages in generated installers
• MD5 checksums are calculated during the compilation
• For downloadable installation components, the download integrity is checked with MD5 checksums
• "Download file" action: Added a "Check for md5sums" property
• Support for Windows processes:
• Added a "Check for running processes on Windows" action that optionally allows the user to terminate those process automatically
• "Install files" action: If running processes are detected, the corresponding window titles are presented in a dialog
• Improvements for file distribution:
• The new Files->File Options tab allows you to define global options for the distribution tree that can be overridden for each entry in the distribution tree
• Launchers now have a configurable overwrite mode for launchers on the Executable info step of the launcher wizard.
• Launchers now have a configurable unix file mode on the Executable info->Unix options step of the launcher wizard
• Distribution tree: Option to add a directory entry into a subdirectory
• Common external content files for downloadable components and external data files. On the General Settings->Media File Options tab, you can enable this feature which is particularly useful for DVDs with multiple media files.
• External data files are now also supported on Mac OS X
• File definition tree: Support for multiple selection, copy mode for drag and drop, quick search, and copy and paste
• Runtime is now shrunk to exclude all unused classed. On the General Settings->Media File Options tab this feature can be disabled.
• Improvements for JRE bundling:
• Added a command line JRE bundle creation utility (createbundle) and a corresponding ant task (com.install4j.CreateBundleTask)
• The JRE bundle creation wizard (Project->Create a JRE Bundle) has been improved in several areas
• "Bundled JRE" step of the media wizard: Added a button to copy a JRE bundle file in a default storage directory to another directory and use a "manual entry" for the copied JRE bundle file.
• "Bundled JRE" step of the media wizard: Added an option to install a statically bundled JRE only if no suitable JRE exists
• Use a private JRE bundle of an existing installation with the same application ID as a fallback if no other JRE can be found
• Many new actions:
• Added a "Create Windows URL link" action
• Added a "Read value from XML file" action
• Added a "Read a key from the Java preference store" action
• Added a "Read a value from the Windows registry" action
• Added a "Wait for HTTP port" action
• Added a "Download and install component" action
• Added a "Create a ZIP file action"
• Added an "Extract a ZIP file" action.
• Added an "Add an executable to the dock" action
• Added an "Add a startup executable on Windows and OS X" replacing the Windows-only "Add an executable to the startup folder on Windows" action
• Improvements for form components:
• Layout groups and tabbed panes in form screens
• All form components with leading labels: Added a "Help text" property. If set, a tool-tip label with a help icon will be added on the right side
• Text field form components: Added a "Prevent empty user input" property that shows a default error message if the user input is empty
• Keyboard shortcuts for form components with user input. Label text can contain mnemonics prefixed with "&" like in "&User" in order to activate the platform-specific keyboard shortcut.
• Form components with user input: Added a "Request focus" property. If selected, the form component is focused each time the form is activated.
• Text field form components: Added a "Enter goes to next screen" property
• Added an "HTML Display" form component
• More flexible configuration of installer applications:
• Installer Applications: Added a "Size client area" property. If selected, the specified size refers to the usable client area of the window and not to the outer dimensions of the window.
• Installer Applications: Added an "Icon can overlap text" property. Now you can use the title bar icon to provide a background for the entire title bar.
• Installer Applications: Added an "Icon anchor" property for the title bar icon.
• Installer Applications: Added "Background color for title bar" and "Foreground color for title bar" properties
• Installer Applications: Added a "Unix mode" property
• Installer Applications: Added properties to customize the Windows version info
• Custom installer applications: Added "Show message when user cancels" and "Cancel message" properties
• More major new features:
• Merging of other projects allow the modularization of your installers
• Index pane for the installer that is configurable in the install4j IDE and via the API
• Support for creating Debian archives
• Other new features:
• New icon set for Windows Vista/Windows 7 and all other non-Windows XP platforms
• Remember window sizes for install4j frames
• Use configured window size for preview dialogs of form screens
• Multiple projects can be now opened at the same time in separate windows. The file association for .install4j project files now works on Mac OS X as well.
• "Display license agreement", "Display information" and "Display text" screens: Files with text are now localizable and can be edited directly in the install4j IDE
• More lenient error handling for the replacement of installer variables where a text is displayed to the user. Instead of throwing an exception for undefined variables, embed an error message in the replaced text
• Quick search in file choosers
• Added new failure strategy for actions: Ask user on failure whether to retry or quit on failure
• Added a "VM options file" step to the launcher wizard to generate a vmoptions file for a launcher. On Mac OS X, the contents are merged automatically with the static VM options.
• Allow URLs in Javadoc configuration
• "Use online documentation" option in Java editor settings dialog to eliminate script warnings with Internet Explorer
• Cross-platform icons can now be defined more flexibly with multiple arbitrary sizes. Note that the icon configuration of installer applications is now in a regular property instead of a separate tab.
• Installation components: The "Mandatory" option has been changed into a "User can change selection state" option for more flexibility
• "Installation components" screen: Added a "Selection change script" property
• "Set the modification time of files" action: Added a "Recursive" property
• "Create program group" action: Configurable menu name for the uninstaller
• "Create program group" action: Added support for URL entries
• Decoupled "Create program group screen" and "Create program group" action, so that multiple "Create program group" actions can be added. Variables are now set by the screen and the action uses those variables.
• "Create program group" and "Program group selection" screen: Added an option to emit a warning if the selected program group already exists
• "Copy files and directories" action: Added a "Show progress" property
• "Display license" screen and "Display text" screen: Added a "Variable name" property to save the actually displayed text to a variable.
• Banner screens: Added a "Banner image anchor" property
• "Install files" action: Added a "Save downloaded files" property to save downloaded installation components for later reuse
• "Install content of ZIP file" action: Added a "File filter" property
• Changed the installation log file format to be less verbose and more readable
• Help argument for installers (-h or-help or /?) that shows the user which common options are available
• Installers: On a fatal error, try to copy the error log file to the media directory and offer the user a button to show the log file immediately
• Add the possibility to see component descriptions in console mode
• Replace installer variables and environment variables in VM parameters and arguments for all generated launchers
• Update installation detection in "Welcome" screen. Added the variable sys.confirmedUpdateInstallation for the user selection in "Welcome" screen. The "Installation location" and "Create program group" screens are skipped if this variable contains Boolean.TRUE.
• Added a /create-i4j-log command line parameter for generated Windows executable to easily create and show a native debug log file
• Installation components can now be hidden from the user. They can be configured in the install4j IDE so that they are initially hidden.
• Unix launchers: Added a INSTALL4J_JAVA_PREFIX environment variable to allow the use of sudo or similar in custom scripts
• VM passthrough parameters (like -J-Xmx512m) are now supported on Unix as well
• Added a check box on the build section to disable LZMA and Pack200 compression for faster builds
• LSB support for service scripts
• The "customCode" sample project now includes an action ManyFeaturesAction that shows most features of the BeanInfo API
• A "mergedProjects" sample project has been added

• Custom installer applications can now be executed from your own code in the same process with com.install4j.api.launcher.ApplicationLauncher#launchApplicationInProcess(...)
• Descriptions in BeanInfo classes can now contain HTML tags for formatting and hyperlinks
• Support for editable text and HTML files, see com.install4j.api.beaninfo.FilePropertyDescriptor#setFileContentType(FileContentType)
• Added com.install4j.api.beans.LocalizableExternalFile for file properties that can be localized by the user in the IDE
• Support for properties with type File[] in all beans, allowing users to select multiple files from the distribution tree
• Java 5 enum properties are now supported without having to use com.install4j.api.beaninfo.EnumerationMapper
• Added com.install4j.api.beaninfo.Install4JBeanInfo#setCategoryOrder(String[]) to override alphabetical category ordering
• Added com.install4j.api.beaninfo.ActionBeanInfo#setFullPrivilegesRequired(boolean)
• Added com.install4j.api.beaninfo.ActionBeanInfo#setComplementaryStartupLink(boolean)
• Added com.install4j.api.beaninfo.Install4JPropertyDescriptor#CONTEXT_COMPONENT and #CONTEXT_DOWNLOADABLE_COMPONENT for receiving installation components IDs in a String property
• Added com.install4j.api.beaninfo.Install4JPropertyDescriptor#CONTEXT_VARIABLE_NAME for properties that hold a variable name. The install4j IDE will offer a selector of pre-defined variables.
• Added com.install4j.api.beans.Anchor
• Added com.install4j.api.beans.LocalizableExternalFile
• Added com.install4j.api.beaninfo.Install4JPropertyDescriptor#CONTEXT_ANCHOR_CORNERS, #CONTEXT_ANCHOR_SIDES, #CONTEXT_ANCHOR_HORIZONTAL and #CONTEXT_ANCHOR_VERTICAL for properties of type com.install4j.api.beans.Anchor
• Added com.install4j.api.formcomponents.LayoutGroup
• Added com.install4j.api.formcomponents.FormEnvironment#getDesignTimeName(LayoutGroup) and #makeParentGroupVisible(FormComponent)
• Configurable error handling for the replace(...) methods in com.install4j.api.beans.AbstractBean. The com.install4j.api.beans.VariableErrorHandlingDescriptor can be used to configure error handling for the replacement of installer variables, localization keys and compiler variables at runtime.
• Added com.install4j.api.context.Context#isRebootRequired()
• Added com.install4j.api.context.Context#getContentDirectory()
• Added com.install4j.api.context.Context#getResourceDirectory()
• Added com.install4j.api.context.Context#runElevated(RemoteCallable, boolean) and #runUnelevated(RemoteCallable)
• Added com.install4j.api.context.Context#isUpdateInstallation() indicating if an update installation was chosen in the "Welcome" screen
• Added com.install4j.api.Util#log(Throwable t)
• Added com.install4j.api.Util#isAdminGroup()
• Added com.install4j.api.Util#hasFullAdminRights()
• Added com.install4j.api.windows.WinUser
• Added com.install4j.api.windows.WinProcesses
• Added com.install4j.api.context.InstallationComponentSetup#setHidden(boolean) and #isHidden
• Added com.install4j.api.context.WizardIndex
• Added com.install4j.api.context.WizardContext#setWizardIndex(WizardIndex) and #setWizardIndexKey(String)
• Added installer events for downloading of files com.install4j.api.event.EventType#BEFORE_DOWNLOAD and #AFTER_DOWNLOAD as well as the event object class com.install4j.api.event.InstallerDownloadEvent with the possibility to get URL, download file, download size and download progress.
• Added com.install4j.api.screens.Screen#isCreateLazily() to avoid screen creation at startup. This is useful if you want to add JAR files with the new method com.install4j.api.context.Context#addToClassPath(File file) after the "Install files" action has run.
• Added com.install4j.api.context.Context#initializeLazilyCreatedScreens() to create all lazily created screens at once.

v4.2.8 [06-11-10]

New features:

• New locale: Romanian
• Comma separated lists are now supported in archive classpath entries, this is useful if compiler variables are used
• API: Added a new event type EventType.FILE_INSTALLATION_STARTED with an event object com.install4j.api.events.InstallerFileInstallationEvent that gives access to total installation size and file count
• API: Added com.install4j.api.events.InstallerFileEvent#getFileSize
• Support for OpenJDK on Windows

• "Install Files" action: Stop services before checking for running processes
• "Installation components" screen: Dependency chains of installation components were not getting updated properly in the tree
• "Run executable or batch file" action: Sometimes a single zero length string argument was passed
• "Uninstall previous installation" action on Mac OS X: The action did not work correctly when the "Require admin user" action was present
• "Installation location" screen: Validation error messages were displayed twice if the directory was selected with the chooser button and the user wanted to proceed anyway
• "Progress display" form component: Fixed a StackOverflow error
• When saving a project to a new location, paths that started with variables were mistakenly prepended with a relative location
• i18n messages were not replaced in splash screen text lines
• Selected and unchangeable components were not installed in console mode
• Fixed internal error 7 when a lot of processes were started at the same time
• Environment variables were not replaced in directory entries of the JRE search sequence
• "Registry and standard locations" search sequence entry did not always choose the newest JVM
• Windows: Creating a 64-JRE bit bundle from a 32-bit install4j IDE did not work correctly
• Windows: Launching media files from the build section in the install4j IDE did not work correctly if UAC was turned on
• If paths in the Installer->Custom code tab contained compiler variables, those variables could not be overridden from the command line
• Classes in extension JARs could not be accessed in scripts
• Unix installers: Improved error message if the unpack200 executable fails
• Set java.library.path explicitly to fix problems on some Windows Server 2003 machines
• JRE bundles: Run -Xshare:dump only for Sun VMs
• Use system language instead of principal language on Mac OS X for system menu and dialogs

v4.2.7 [02-13-10]

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

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

v4.2.6 [12-16-09]

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

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

v4.2.5 [11-19-09]

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

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

v4.2.4 [10-05-09]

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.

• 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