Runtime page

The Runtime page shows information about run-time libraries. When packaged, platform plug-ins deliver all of their Java classes in JAR libraries. This page defines how the classes that are in source folders during the design time are packaged into the libraries. One source folder and one library have already been set during the project creation by the wizard. You can define more on this page.

Runtime editor page

Note:  The information about the source folders that should be compiled to produce the libraries is actually stored in a separate file (build.properties). When you change this information, build.properties will be updated. This can only happen if the file is not in use. If it is, the manifest editor will indicate that the file is in use and you will only be able to browse the information.

By default, a library is of type 'code', and thus assumed to contain executable code and resources.  Accessing anything from such a library causes the activation of the plug-in and all its dependencies.  If a library in your plug-in is not to contain executable code, e.g. libraries that hold translated NL strings only, it should be marked of type 'resource'.  Accessing a 'resource' from such a library does not activate the plug-in, thus greatly improving performance.

You can also determine exporting rules for your libraries. By default, no classes in your libraries can be seen by others. This is appropriate if your plug-in is not meant to be extended. If your classes should be visible to other plug-ins, the libraries must be exported. You can export the entire library, or just some portions that match the provided content filters (for example, com.example.*).

Declaring package prefixes for a library results in 10-15% increase in class loading speed.

 
Copyright IBM Corporation and others 2000, 2003