The Universal Plugin Manager (UPM) provides a ton of really useful information to plugin developers on its OSGi tab. The OSGi tab is a "hidden" feature which is not visible by default because it is not relevant for the average system administrator.
The OSGi tab is available in UPM 1.3 and later.
For more information about OSGi and its use in the Atlassian Plugin Framework, please read about OSGi, Spring and the Plugin Framework.
Use the Atlassian Plugin SDK
The OSGi tab is automatically visible when using the Atlassian Plugin SDK.
There are two easy ways to enable the OSGi tab:
atlassian.dev.mode
flag set to true/plugins/servlet/upm#osgi
in your web browserA cookie is stored upon loading the tab for the first time, marking the tab as visible for future use.
Listed on the OSGi tab is a collection of installed OSGi bundles. The bundles are represented by their ID and key (which matches their plugin key).
Expanding an OSGi bundle reveals a great deal of information, including the bundle's version and symbolic name.
Additionally, depending on the information present in the bundle's manifest, you may or may not see the following expandable areas:
Each of these expandable areas, when appropriate, will link to other bundles which relate to the bundle in use.
In addition to viewing useful bundle information, the OSGi tab is an excellent resource for debugging plugin deployment errors.
For example, if you see a ClassNotFoundException
thrown upon plugin startup:
Import-Package
section.Additionally, it is possible that you are importing the right packages but of the wrong versions. With the OSGi tab you can determine exactly which version of each package is in use, and from which bundle the package is provided.
OSGi, Spring and the Plugin Framework
Developing for the Marketplace
Rate this page: