General Settings - Java Version | ![]() ![]() ![]() |
![]() | On this tab of the General Settings step you enter the version requirements and the search sequence for the JRE or JDK that apply to your installers and application launchers. |
![]() |
In the Java version section, you can constrain the version of the
Java VM.
The maximum Java version can be entered with less numeric detail than the minimum Java version to prevent the use of a higher major or minor release. For example, a minimum version of 1.4.1 and a maximum version of 1.4 ensures that the highest available 1.4.x >= 1.4.1 JRE is used, but not a 1.5 JRE. Similarly, a minimum version of 1.4.1_03 and a maximum version of 1.4.1 ensures that the highest available 1.4.1 >= 1.4.1_03 JRE is used, but not a 1.4.2 JRE. By default, JREs with a beta version number or JREs from an early access release cycle will not be used by the launcher. If you would like to enable the use of these JREs, please check the option allow JREs with a beta version number. |
![]() |
The JRE search sequence determines how install4j searches for a JRE on the target system.
New configurations get a pre-defined default search sequence.
install4j has a special mechanism which allows you to bundle JREs with your media files.
If you
choose a particular JRE for bundling
in one of the media file wizards,
this JRE will always be used first and you do not need to adjust the search sequence yourself.
If you have problems with JRE detection at runtime, please see the help topic on error handling for a description on how to get diagnostic information. The following types of search sequence entries are available:
The control buttons on the right allow you to modify the contents of the search sequence list:
|
![]() | A build will not be possible until all required fields have been completed. If a required field is missing when starting a build, this tab will be displayed with a warning message. |
![]() ![]() ![]() |