The first step in using OSGi profiles with Bundlor is to create a file that contains a textual
representation of the two properties that make up an OSGi profile:
org.OSGi.framework.bootdelegation. What you include in this file is up to you, but
typically you start with the OSGi profile of the OSGi runtime you are using, and then customize it to fit
If you are using Virgo as your OSGi runtime, you can start by copying the section of the file
$VIRGO_HOME/configuration/java6-server.profile that refers to the two properties and pasting it
into your text file. If you are using another runtime, consult their documentation.
The following snippet shows a partial OSGi profile for Virgo; for clarity only a few packages are shown. The example shows the format in which you should create your own OSGi profile file.
org.OSGi.framework.system.packages = \ org.eclipse.virgo.osgi.extensions.equinox.hooks,\ javax.accessibility,\ javax.activation,\ javax.activation;version="1.1.1",\ javax.activity,\ javax.annotation,\ ... org.OSGi.framework.bootdelegation = \ org.eclipse.virgo.kernel.authentication,\ com.sun.*,\ javax.xml.*,\ ...
Once you've created your OSGi profile file, the method of passing it to Bundlor depends on the front end you are using to generate a manifest. For detailed information about using the various front ends, see Chapter 4, Usage.