I am developing an application on top of NetBeans platform. My application consists of few clusters and I would like to be able to access JARs from one of those clusters when booting. I would like to keep those JARs in lib folder of that clusters in the same manner as the (NB) platform. In order to do that I added those JARs to the classpath by using the --cp:p option.

However, it seems to me that the options --cp:p <classpath> and --cp:a <classpath> are not much useful in reality. The reason is that the <classpath> needs to be an absolute path to the JAR(s) otherwise I am not able to use a common .conf file for both Windows and Linux builds. On Windows the nbexec process uses the application install directory as its working dir and as such a relative path is resolved using app install dir. On the other hand, on Linux the working directory from which was the script app.sh started is used and this can be an arbitrary directory since I can run the app using, e.g., ./bin/app.

Therefore, it would be useful to have a relative classpath path resolved by the launcher using a well known dir, e.g., the app install dir. Or maybe better to be able to use some token to denote that a path should be resolved by the launcher, e.g., using app install dir or directly a cluster dir.