Packaging

Developers must package their custom plug-ins so they can be distributed for installation and use.

Add the Workbench for Eclipse API as a dependency

Developers must include the Workbench for Eclipse API and Workbench API as a dependency of any custom plug-in they create that uses the Workbench for Eclipse API. This can be done in two different ways within a plug-in’s MANIFEST.MF file:

1. Open the plugin.xml file using the Plug-in Manifest Editor.
2. On the Dependencies tab of the editor, do one of the following:
   
   • Add the com.compuware.api.topaz.eclipse and com.compuware.api.topaz bundles to the list of required bundles
   • Add the specific packages of the com.compuware.api.topaz.eclipse and com.compuware.api.topaz bundles that are used by the custom plug-in to the list of imported packages

Create a feature

Developers must create a custom feature so that their custom plug-in can be included in a p2 repository for installation by users. A feature can be created from the File->New menu within the Workbench for Eclipse, Eclipse, or RDz.

Once the custom feature is created:

1. Open the feature.xml file using the Feature Manifest Editor.
2. On the Plug-ins tab of the editor, add the following:
   
   1. The custom plug-in
   2. The com.compuware.api.topaz.eclipse plug-in
   3. The com.compuware.api.topaz plug-in
   4. Any other plug-ins or fragments that the custom plug-in requires

Export the feature in a p2 repository

Lastly, developers must create a p2 repository that users can point to for installation of the developer’s custom feature. A p2 repository can be created in two different ways:

1. On the Overview tab of the Feature Manifest Editor, click the Export Wizard link under the Exporting section.
2. Use the File->Export... menu and choose Deployable features under the Plug-in Development category.