General
section of this step:
-Dmyapp.myproperty=true
or -Xmx256m
).
Note: You must quote parameters that contain spaces. Please quote the
entire parameter like "-Dapp.home=${launcher:sys.launcherDirectory}"
and not just
the value. Incorrect quoting will lead to failure of the launcher.
Please read the help topic on VM parameters for more information on how install4j can help you with adjusting the VM parameters at runtime.
-J[VM parameter]
(e.g. -J-Xmx512m
),
select the Allow VM passthrough parameters
check box.
Note: This setting applies only to Windows launchers. On Unix platforms
you can use the INSTALL4J_ADD_VM_PARAMS
environment
variables to add VM parameters to the launcher. On macOS, you can edit the
Info.plist
file to change the VM parameters.
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.