Using Pax Runner Configuration Tab

If you installed the Eclipse Plugin UI feature, the tab shown bellow has been added to OSGi Framework Launch Configuration dialog. This configuration tab allows easy setup of divers Pax Runner startup options as well as managing the bundle provisioning. Look bellow for details about configuration options.

Options

Overwrite

Pax Runner downloads all bundles to be provisioned as well as jars/bundles required by the running framework into a local cache so a second+ run will not do the download again. To override this behavior you can set on of the 3 toggles:

• All — removes all cached bundles (files), so those bundles will be downloaded again;
• User — removes all cached "user" bundles (bundles that you specified by using the provisioning urls), so those bundles will be downloaded again;
• System — removes all cached "system" bundles and files (jars and bundles that makes up the started platform), so those bundles will be downloaded again.

Log

Specify the logging level that will be used by Pax Runner. Note that this logging level refers only to Pax Runner not to the started framework nor any logging service/framework that will be available in the started framework.

Profiles

Pax Runner supports the notion of profiles, which are sets of bundles that you "usually" use in your development (read more). You can select any combination of profiles that you need in your session. So, for example by selecting log and web your will automatically get in the started framework a logging service (Pax Logging) and an http service (Pax Web). You can read more about what gets deployed (and version) in each framework page: Equinox, Felix, Knopflerfish, Concierge.
(if you consider that also other profiles should be made available do not hesitate to add an issue in jira)

Provisioning

Pax Runner supports bundle provisioning from different sources, such as http, file system or maven, via scanners by scanning for one bundle, scanning a plain text file, scanning a directory or zip or a Maven POM. The provisioning section will allow you to configure what bundles will be provisioned.
Once a provisioning url has been added to the table (via one of the Add buttons) you can:

• Select the bundle to be deployed or not via the checkbox from the first column
• Choose if you want the bundle to be started or not once it is deployed (click on the column to change)
• Choose the start level at which the bundle will be started. By default it will be started at the level you had specified on the first tab of the configuration dialog (click on the column to change)
• Choose if you want the bundle to be updated (removed from the cache and re-downloaded) ( (click on the column to change)
• Edit the provisioning url by using the Edit button
• Remove the provisioning list form the list by using the Delete button (note that the table support multiple rows selection, so more bundles can be removed in one shot)

As there are different ways to provision bundles there are task specific Add buttons:

• Add — manually enter any provisioning url
• Add Bundle — select a jar (bundle) from file system. This will be provisioned using Bundle Scanner
• Add File — select a text file or any file that conforms and will be provisioned using File Scanner
• Add POM — select a Maven 2 POM file (pom.xml, *.pom). This will be provisioned using Maven POM Scanner
• Add Dir — select a directory using the bundles to be provisioned. This will be provisioned using Directory Scanner
• Add Maven — not yet implemented but will allow you to browse a Maven 2 local or remote repository and select a Maven artifact to be provisioned.