|
By default, all custom code is packaged separately into the installer. If your custom code uses the same libraries
as your installed launchers (such as a database driver), these libraries are duplicated, increasing the size of
your installer. If you would like to avoid this duplication you can select the "use installed JAR files where
possible" check box. In that case, the install4j compiler checks if a custom code JAR file location is equal to
a JAR file that was packaged in the distribution tree and doesn't package it again.
Note: The installed JAR files will be available only after the "Install files" action has run.
All your custom code that depends on these JAR files must be placed after the "Install files" action, otherwise
a runtime error will occur. If you use installation components, these libraries should be part of a mandatory
component.
The "use installed JAR files where possible" option changes the initialization strategy of the installer.
If selected, the installer initialized screens and actions up to the "Install files" action at startup and the
rest after the "Install files" action has run. If not selected, all screens and actions are initialized at
startup.
|