If the build fails because the Java compiler could not be found, copy the file
tools.jar from a JDK installation to
<DT_HOME>/jre/lib/. If the Client is running from Webstart, copy
tools.jar to the
lib directory of your local JRE installation.
Yes. The Plugin life cycle methods may be executed at any time and from multiple threads. Consider this possibility when writing custom Plugin code.
If the bundle is only used by one Plugin, it is best to add it as a private library, because a library is part of the Plugin bundle and that eases Plugin deployment.
If the bundle is used by multiple Plugins and is of considerable size, add it as a bundle dependency, because this enables sharing of the bundle between different Plugins. However, this may also break the isolation of the Plugins that use the bundle, especially if the bundle has any sort of state.
The secure option, though it consumes more resources, is to add the bundle as a library to each Plugin that uses it.
After building the Plugin, switch to the Installed tab and use Import Jar to import the built Plugin JAR file. The JAR file can be found in the
build folder of the Plugin project.
Do this only as a workaround. Installing an untested plugin is not recommended.