General
section of this step:
-Dmyapp.myproperty=true
or -Xmx256m
).
There are several runtime-variables you can use to specify runtime directories:
These variables can be especially useful for adding JAR files to the bootclasspath.
exe4j has the ability to add specific VM parameters depending on the Java version. To set this up, click on the Configure version specific VM parameters button. In the dialog, add rows for each Java version that should receive specific VM parameters. The comparison checks if the Java version string starts with the specified characters, so "1.8" will match "1.8.0_60", for example. These VM parameters are added after the common VM parameters so you can use them to override common settings.
In addition to these VM parameters, a parameter file in the same directory as the executable
is read and its contents are added to the existing VM parameters. The name of this parameter
file is the same as the exe file with the extension *.vmoptions
.
For example, if your exe file is named hello.exe
, the name of the VM
parameter file is hello.vmoptions
. In this file, each line is
interpreted as a single VM parameter. For example, the contents of the VM parameter
file could be:
-Xmx128m -Xms32m
It is possible to include other .vmoptions
files from a .vmoptions
file with the
syntax
-include-options [path to other .vmoptions file]
.vmoptions
file right next to the executable.
This allows you to to centralize the user-editable VM options for multiple launchers and to have
.vmoptions
files in a location that can be edited by the user if the installation directory is
not writable. You can use environment variables to find a suitable directory, for example
-include-options ${APPDATA}\My Application\my.vmoptions
-include-options ${USERPROFILE}\.myapp\my.vmoptions
In addition to the VM parameters you can also modify the classpath in the .vmoptions
files with the
following options:
You can use environment variables in the VM parameters with the following syntax:
${VARIABLE_NAME}
where you replace VARIABLE_NAME with the desired
environment variable.
-J[VM parameter]
(e.g. -J-Xmx512m
),
select the Allow VM passthrough parameters
checkbox.
Class path
section of this step you can configure the
class path and the error handling for missing class path entries. The class path
list shows all class path entries that have been added so far. The following types of
class path entries are available:
The symbol
prepended to an entry
indicates that an error with that entry will lead to a startup failure with an error
message displayed to the user. The control buttons on the right allow you to
modify the contents of the class path list:
INS
)DEL
)ALT-UP
)ALT-DOWN
)To change the error handling mode of a class path entry, select the class path entry and press Toggle 'fail on error' right below the class path list or choose the corresponding menu item from the context menu.