Changing Build Path Options
Currently I am working on a plugin that requires a Native Library Location to be configured for one of the libraries. I can do this in Eclipse and it works fine, but the classpath option is removed when the plugin is built in dynaTrace. I can get past the need for the class path option by manually adding the required dll to the java path, but it would be much more preferable if I could specify the class path. Does anyone know how to make sure that the class path options stay after building in dynaTrace?
Thanks,
Brian Perrault
The reason for this behavior is that the OSGi bundle classpath is recreated from scratch (using the configured .jar libraries) when the plugin is built with the dynaTrace client. The only (ugly) workaround I can offer right now is to build the plugin in dnyaTrace, open the built .jar and then add your classpath extension to the manifest within the jar, only then deploy it.
