install4j 4.2.5
INSTALLER BUILDER FOR JAVA APPLICATIONS.
Exceptional ease of use
Some installer builders require that you first become an expert in building installers. Not so with install4j, where all configuration steps are intuitive and self-explanatory. The install4j IDE guides you naturally through the process of gathering required information. Building an installer that works is a matter of minutes. Nonetheless, you have a powerful arsenal of functionality at your disposal when you need it.
install4j uses wizards to guide you through important decisions
Beautiful installers
The installer is the first thing your users see of your application. A smooth installation experience is an important step in creating happy users and a successful product. A substandard installer, however, can ruin the initial impression that is so important for the image of a product. With install4j, your installers will look beautiful and feel natural to users on all platforms.
install4j provides a first-class user experience
Rich screen & action system
With install4j, you can configure the screen flow for the installer and uninstaller in any way you like. install4j provides screens and actions for a wide variety of use cases and allows you to create your own actions directly in the install4j IDE. Actions can be attached to each screen, making install4j a visual programming system far more powerful than traditional installer builders.
Installers are built with screens and actions
Fully flexible auto-updaters and custom applications
install4j offers several templates for updaters that enable you to create an auto-update solution for your application with just a few clicks. Auto-updaters are fully customizable, so they can support your special requirements for a large number of scenarios. More generally, install4j supports the creation of custom installer applications that are packaged with your application.
Screens can be configured for installer and uninstaller
Simple creation of custom screens
Querying information from the user that`s specific to your application does not have to be hard. Besides programming your own custom screens, install4j includes a unique concept of form screens that look good and are easy to configure. With its powerful variable system, install4j enables you to use the entered information in other screens and actions. Creating a user interface cannot get any easier than this.
In install4j you can create form screens with no coding
Native launcher generation
install4j generates launchers for your applications that are native on every supported platform: Windows executables are compiled with our exe4j technology, state-of-the-art Unix shell scripts are created for Unix platforms and application bundles blend in seamlessly on Mac OS X. These launchers offer the most flexible JRE-detection on the market and are integrate with many other features in install4j.
Launchers are configured once and generated for each media file
Advanced JRE bundling
One of the core requirements for a Java-aware installer builder is the ability to bundle a JRE with the installer. With features like download-on demand, Pack200 compression or shared installations of JRE bundles, install4j stands out in this area as well. Pre-packaged JRE bundles can be easily downloaded from within the IDE making JRE bundling a one minute exercise.
JRE bundling can be configured for each media file
Superb cross-platform support
Deploying an application to multiple platforms is a complex endeavor. install4j eases this burden by several orders of magnitude. You define a common installer for the entire project and specify platform-specific information in the media wizards. Even if you only require the Windows Edition at first, by choosing install4j you keep all your options open for targeting multiple platforms.
Platform-specific information is configured in the media wizards
Extensive i18n support
install4j fully supports you in localizing your installer to multiple languages. It offers a large number of installer languages and an easy mechanism to introduce new keys for your own messages in the installer. You can build single-language or multi-language installers that detect the actual language at runtime.
With installj you can build multi-language installers
Extensibility
install4j is extensible. With its JavaBeans-based extension model and its well-documented API, you can add your own actions, screens and form components to the component registries in install4j. All pre-defined components in install4j are programmed that way. With this flexibility, you can quickly integrate your own code into the installer or create extensions that can be reused in multiple projects
What is new in 4.2.5 software version? - 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









