Note: this advanced option screen is reachable by selecting the
"JRE" step and choosing
"Search Sequence" from the
[Advanced options]
popup menu or by clicking directly on the index.
In this step of the exe4j wizard, you can configure the
way the exe4j executable looks for an appropriate JRE or JDK to start your Java
application. The versions requirements for the JRE are specified in a
different step.
|
It is possible to generate a log file that contains information about the JRE search sequence and any
potential problems.
In order to switch on logging, please define the environment variable
EXE4J_LOG=yes and look for the newest text file whose name starts with
i4j_nlog_ in the Windows temp directory.
This information can be used for debugging purposes. If you have a problem
with JRE detection, please send this log file along with your support request.
An easier way for a user to create a log file is to start the launcher with the
/create-i4j-log argument. The launcher will notify the user where the log is created and
will offer to open an explorer window with the log file selected. After the message box, the launcher will
continue to start up.
|
|
Tip: To distribute your own JRE, simply put the JRE in your distribution and
define a directory search
sequence entry with the appropriate relative path (e.g. jre) as the first
item.
|
|
If the entire search sequence fails, exe4j will try the location defined by the
environment variable EXE4J_JAVA_HOME. If that fails too, an
error message will be displayed asking the user to define this variable. To
supply a custom variable, define an appropriate environment variable search sequence entry
and customize the corresponding error message in the
messages step of the wizard.
|