I need to specify the jars for my application dynamically (at runtime) and I would like to use wildcarding so that all jars found within the wildcarded directory will be included in the classpath. This capability is supported when launching the JVM from the command line but I can't seem to get it to work with the native launcher.
For example, if I have a jar called foo.jar that contains my main class com.foo.Main, on the command line I can specify the following to launch my application:
java -classpath *; com.foo.Main
Executing this from the command line (assuming that the command is run in the directory where foo.jar resides) works correctly. However, I cannot figure out how to express the same thing using the native launcher for Advanced Installer. In my application, I have all of my jars in a directory called "jars" and I would like to tell Advanced Installer to include all jar files found in that directory in the classpath. I *DO NOT* want to explicitly declare the jars (through the GUI) when my application installer is being built. In my application, the jars included in the classpath may change after it has been installed so I need flexibility in the classpath declaration.
I read a solution described here: http://www.advancedinstaller.com/forums ... ath#p26299 but what that seems to be explaining is a way to dynamically add directories to the classpath, when what I actually want is to either declare individual jars at application start time or use wildcards so that all jars found within a directory will be included in the classpath.
I have been using your tool for several weeks and I *really* like it. This classpath issue is the last problem that my application needs to solve.
FOLLOW US
Get the latest news in Application Packaging