<html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Editing the Manifest</title><meta content="DocBook XSL Stylesheets V1.76.0" name="generator"><link rel="home" href="index.html" title="Virgo Tools Guide"><link rel="up" href="ch06.html" title="Chapter 6. Developing OSGi Bundles"><link rel="prev" href="ch06.html" title="Chapter 6. Developing OSGi Bundles"><link rel="next" href="ch07.html" title="Chapter 7. Developing OSGi Bundles using Plug-in Development Environment (PDE)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><td align="left" width="20%"><a accesskey="p" href="ch06.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch07.html">Next</a></td></tr></table><hr></div><div class="section" title="Editing the Manifest"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tooling-developing-editing-manifest-mf"></a>Editing the Manifest</h2></div></div></div><p> | |
The Tools provide a Bundle Manifest Editor that assists the developer to create and edit MANIFEST.MF files. The | |
editor understands the Virgo Runtime Environment specific headers like | |
<code class="code">Import-Library</code> | |
and | |
<code class="code">Import-Bundle</code> | |
and provides content assist features while editing source code. Furthermore a Eclipse Form-based UI is also | |
available. | |
</p><p> To open the Bundle Manifest Editor right click a MANIFEST.MF file and select "Bundle Manifest Editor" from the | |
"Open With" menu. </p><p> | |
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3> | |
Please note that the Virgo Runtime Environment specific manifest headers appear in green color to distinguish them | |
from those headers defined in the OSGi specification. This also makes navigating much easier. | |
</div><p> | |
</p><p> | |
<img src="images/tooling-manifest-source-editor.png"> | |
</p><p> 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 Runtime Environment. Therefore it is important to target the | |
project or PAR to a specific Virgo Runtime instance to indicate to the tooling which bundle repository | |
to use. </p><p> | |
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3> | |
If a OSGi bundle project is not targeted to a Virgo Runtime 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. | |
</div><p> | |
</p><p> | |
<img src="images/tooling-manifest-form-ui-editor.png"> | |
</p><p> 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. </p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch06.html">Prev</a> </td><td align="center" width="20%"><a accesskey="u" href="ch06.html">Up</a></td><td align="right" width="40%"> <a accesskey="n" href="ch07.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%"> </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> </td></tr></table></div></body></html> |