Mastering Java Development: Opening the ‘Include Path Files’ Interface

Table of Contents

• Introduction
• Registration
• Using Advanced Installer
  • GUI
  • Working with Projects
  • Installer Project
    * Product Information
    * Resources
    * Files and Folders
    * Tiles
    * Java Products
    * Java Settings
    * Java Product Settings
    * Preferred JRE Version Dialog
    * Environment Variable Picker Dialog
    * Add Classpath Files
    * Java Virtual Machine
    * Mac OS X settings
    * Java Product Localization
    * Registry
    * File Associations
    * Assemblies
    * Drivers
    * Services
    * Package Definition
    * Requirements
    * User Interface
    * System Changes
    * Server
    * Custom Behavior
  • Patch Project
  • Merge Module Project
  • Updates Configuration Project
  • Windows Store App Project
  • Modification Package Project
  • Optional Package Project
  • Windows Mobile CAB Projects
  • Visual Studio Extension Project
  • Software Installer Wizards - Advanced Installer
  • Visual Studio integration
  • Alternative to AdminStudio/Wise
  • Replace Wise
  • Migrating from Visual Studio Installer
  • Keyboard Shortcuts
  • Shell Integration
  • Command Line
  • Advanced Installer PowerShell Automation Interfaces
• Features and Functionality
• Tutorials
• Samples
• How-tos
• FAQs
• Windows Installer
• Deployment Technologies
• IT Pro
• MSIX
• Video Tutorials
• Advanced Installer Blog
• Table of Contents

Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Add Classpath Files Dialog

Wildcard Path

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.

This Formatted Type field can be edited using Smart Edit Control .

The location of the files can be absolute orrelative. If the location will not point to anabsolute path, it is considered as relative to the Java Product folder.

Examples:

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.

• [lib_DIR]\*.jar
• 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 pathlib\*.jar.
• *.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 locationrelative 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.

Did you find this page useful?

Please give it a rating:

Thanks!

Report a problem on this page

Information is incorrect or missing

Information is unclear or confusing

Something else

Can you tell us what’s wrong?

Send message

Also read: