The following parameters apply to the classpath used by the
- Classpath. Specify the classpath required by the
application. Multiple entries are delimited by semi-colon. Each
entry in the classpath could be a JAR or ZIP file. If the entry is
a directory, all the JAR and ZIP files in that directory will be
dynamically appended to the final classpath at runtime. This
operation is recursive, hence all subdirectories will also be
searched for JAR or ZIP files.
If you are bundling a specific JRE with your application, there is
another way to specify the class files required by your
application. For more information, refer to An alternative approach to
This field is required.
- Embedded JAR files Specify the JAR or ZIP files you wish
to embed into the final executable. When the executable is run for
the first time, these JAR files will be extracted into a temporary
directory and appended to the classpath. Subsequently, as long as
the JAR files are not modified or removed, the extraction step will
be skipped. Note that this could increase the size of the final
executable tremendously, depending on the total size of the
embedded JAR files.
Please refer to JAR files
embedding for more information on this topic.
- Extract to Specify where to extract the embedded JAR
files to. By default, they are extracted to the system temp folder.
You can change this parameter to extract the embedded JAR files to
the application folder (which is the same folder where the EXE file
resides), or to the application temp folder (which is a temporary
subfolder within the application folder).
- Delete JAR files when EXE terminates Normally, embedded
JAR files are not deleted once they are extracted into a temporary
directory. This enhances startup speed because the extraction step
will be skipped when the application is run the next time. However,
if you want the embedded JAR files to be removed when the
executable terminates, select this checkbox.