EJ Technologies Install4j MultiPlatform Edition v6.1.3
EJ Technologies Install4j MultiPlatform Edition v6.1.3 | 72 Mb
Install4J - a powerful platform and compiler software installer Java, that generates native installers and application launchers for applications Java. Install4J in easy to use. Uses tight integration into the target platform, flexible management JRE and deployment options.
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.
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.
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.
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.
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.
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.
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.
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.
RELEASE 6.1.3
New features:
•Mac OS X: DMGs files are now signed in addition to the contained launchers. This is needed for folder archives to work on Mac OS X 10.12.
•Mac OS X: All signatures are now timestamped and SHA-2 is used for signing, except when the old Apple JRE is used
•systemd support for services on Unix/Linux
•Implemented auto-start for services in Linux package archives (RPM/DEB). This only works with systemd and can be disabled in the launcher wizard under Executable info->Unix options.
•"Wait for HTTP server" action: Added a "Variable name for response code" property
•Added the possibility to place a ".packoptions" file next to a jar file, with options for the Pack200 packer. Currently only -P und --pass-file= are supported.
Bugs fixed:
•"Show URL" action: The action did not fail if the browser could not be opened
•"Display text" screen: For unresolved variables in the "Info text" property, an exception was thrown instead of showing an error message in the displayed text
•"Display text" screen: Installer variables in the "Info text" property were not updated when the screen was activated
•"Installation components" screen: In console mode, it was not possible to only install mandatory components. Now "X" is used to mark mandatory components and can be given as an answer
•Mac OS X: Partially uninstalled JRE plugins were not detected correctly
•Mac OS X: If no AppleScript engine was found, an NPE was logged instead of a proper error message
•Windows: Fixed DLL injection prevention for the installer on Windows 7
•Windows: After a failed elevation restart, all files in the installer directory could be deleted
•Security enhancement: By default, the Windows and Unix installers do not read ".vmoptions" files anymore
•Custom code could be deleted too early during the uninstallation
•Linux: Calling an installer with the -help argument did not work if no X-server was present
•Actions lists did not work in unattended mode
•When action lists were executed by form components, a screen navigation history entry was created, so that the back button of the screen required multiple clicks to to go to the previous screen
•context.getWizardContext().setNextButtonEnabled(...) and .setPreviousButtonEnabled(...) as well as changing the enabled state of other form components on the same screen did not work from action lists in form components
New features:
•Mac OS X: DMGs files are now signed in addition to the contained launchers. This is needed for folder archives to work on Mac OS X 10.12.
•Mac OS X: All signatures are now timestamped and SHA-2 is used for signing, except when the old Apple JRE is used
•systemd support for services on Unix/Linux
•Implemented auto-start for services in Linux package archives (RPM/DEB). This only works with systemd and can be disabled in the launcher wizard under Executable info->Unix options.
•"Wait for HTTP server" action: Added a "Variable name for response code" property
•Added the possibility to place a ".packoptions" file next to a jar file, with options for the Pack200 packer. Currently only -P und --pass-file= are supported.
Bugs fixed:
•"Show URL" action: The action did not fail if the browser could not be opened
•"Display text" screen: For unresolved variables in the "Info text" property, an exception was thrown instead of showing an error message in the displayed text
•"Display text" screen: Installer variables in the "Info text" property were not updated when the screen was activated
•"Installation components" screen: In console mode, it was not possible to only install mandatory components. Now "X" is used to mark mandatory components and can be given as an answer
•Mac OS X: Partially uninstalled JRE plugins were not detected correctly
•Mac OS X: If no AppleScript engine was found, an NPE was logged instead of a proper error message
•Windows: Fixed DLL injection prevention for the installer on Windows 7
•Windows: After a failed elevation restart, all files in the installer directory could be deleted
•Security enhancement: By default, the Windows and Unix installers do not read ".vmoptions" files anymore
•Custom code could be deleted too early during the uninstallation
•Linux: Calling an installer with the -help argument did not work if no X-server was present
•Actions lists did not work in unattended mode
•When action lists were executed by form components, a screen navigation history entry was created, so that the back button of the screen required multiple clicks to to go to the previous screen
•context.getWizardContext().setNextButtonEnabled(...) and .setPreviousButtonEnabled(...) as well as changing the enabled state of other form components on the same screen did not work from action lists in form components
Only for V.I.P
Warning! You are not allowed to view this text.