5.2 Editing the Manifest
Prev | 5. Developing OSGi Bundles | Next

## 5.2 Editing the Manifest

The Tools provide a Bundle Manifest Editor that assists the developer to create and edit MANIFEST.MF files. The editor understands the Virgo Server for Apache Tomcat specific headers like `Import-Library` and `Import-Bundle` and provides content assist features while editing source code. Furthermore a Eclipse Form-based UI is also available.

To open the Bundle Manifest Editor right click a MANIFEST.MF file and select "Bundle Manifest Editor" from the "Open With" menu.

| Note
Please note that the Virgo Server for Apache Tomcat specific manifest headers appear in green color to distinguish them from those headers defined in the OSGi specification. This also makes navigating much easier.

The content assist proposals in the source tab as well as in the UI-based tabs are resolved from the bundle and library repository of an installed and configured Virgo Server for Apache Tomcat. Therefore it is important to target the project or PAR to a specific VTS instance to indicate to the tooling which bundle repository to use.

| Note
If a OSGi bundle project is not targeted to a VTS instance, either directory or indirectly via a PAR project’s targetting, the manifest editor will not be able to provide content assist for importing packages, bundles, and libraries.

The Dependencies tab of the Bundle Manifest Editor enables the user to easily download and install bundles and libraries from the SpringSource Enterprise Bundle Repository by using the "Download..." buttons next to the "Import Bundle" and "Import Library" sections.

Prev | Up | Next
5. Developing OSGi Bundles | Home | 6. Developing PARs