In this field, you can declare custom locations with wildcard support. The files selected by this wildcard will be added to the "Classpath" parameter of your Java Application at the application's runtime.
The location of the files can be absolute or relative. If the location will not point to an absolute path, it is considered as relative to the Java Product folder.
In these examples we suppose:
The Java Product directory is placed in Application Folder from the Files and Folders Page - Installer Project; The lib folder is located in the Java Product directory and contains multiple JAR files. The lib_DIR identifier is assigned to the lib folder.
- In this case, all the JAR files from the lib folder will be added to the "Classpath" parameter. This is considered an absolute path. This is equivalent to the relative path lib\*.jar.
- All the JAR files from the Java Product folder will be added to the "Classpath" parameter. This is considered a relative path. This syntax is equivalent to the absolute path [APPDIR]\*.jar.
Using Absolute Paths
Based on the first example, the location [lib_DIR]\*.jar will be resolved at the application's runtime and it will point to absolute paths. The files selected by the wildcard will also be added to the "Classpath" parameter at the runtime of the application. If the lib folder is renamed or moved in Advanced Installer, the location will still be correctly resolved and the files will be added at the application launch time.
Using Relative Paths
Based on the first example, if a relative path is being used the lib\*.jar will be resolved at the application's runtime and will point to a location relative to the Java Product's folder. If the lib folder no longer resides in the Java Product directory or has been renamed, the location cannot be correctly resolved and no file can be added to the "Classpath" parameter.