Adding Bundle Resources

Since deployment packages can contain bundle resources, the Deployment Package Editor enables you to add different OSGi bundles in the Deployment Package Project file and modify their properties. Information about the contained resources is placed in the so-called Name section of the manifest file and can be viewed in the Manifest tab of the Deployment Package Editor. By default, the initially created Deployment Package Project file holds no bundle entries.

The bundles which you will add to a deployment package might be in either of the following formats:

To add a new bundle resource to a Deployment Package Project file:

  1. Launch the Deployment Package Editor by double-clicking on a Deployment Package Project file (.dpp) in one of the navigation views.
  2. Go to the Bundles tab in the activated editor.
  3. To add a bundle to the package, click the New button. An empty row appears in the bundle table.
  4. In the empty row specify the following properties for the bundle resources contained in the targeted deployment package:


  5. Figure 1: Adding bundle resources to a deployment package.

  6. Save the Deployment Package Project file to store the changes made in connection with the bundle resources present in the targeted deployment package.

Automatic Update Detection

If a bundle, added to a deployment package, is generated from an Eclipse plug-in project with its JAR file name following the versioning convention implemented in the Eclipse plug-in development environment (PDE), the Deployment Package Editor will automatically detect changes in the version segment of the JAR file name and will consider such changes as JAR file updates. In such case, when you open a Deployment Package Project file or try to create a deployment package which contains bundle resources with changed file names, the editor informs you of this change by displaying the following dialog:


Figure 2: Detected changes in the JAR file names of bundle resources participating in a deployment package.

It is recommended, but not obligatory, to use the newly discovered JAR file updates. Otherwise, your attempts to create a deployment package JAR holding bundle resources updated in this way will fail as the editor will not be able to locate them in the file system.

Tip: To automatically accept bundle updates related to the version part of bundle file names, check the Accept bundle version updates automatically box in the mTookit preferences. See "Configuring Deployment Package Editor" for information about Deployment Package Editor preferences.

Common Errors

When adding new bundle resources to a deployment package, you may encounter some error messages. They may have to do with the following most common errors:

Deployment Package Overview
Deployment Package Editor

Creating a Deployment Package Project File
Generating a Deployment Package
Quick Deployment Package Build
Exporting Deployment Package Build Files
Configuring Deployment Package Editor
Plug-in Project
Plug-in Project from Existing JAR Archives