Running as an "Eclipse Application"
does not give you the option to select which bundles should be automatically
started. This type of launcher expects all the bundles in the system
to be lazy-started (except the boot strap bundles specified in osgi.bundles
See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=136005
which discusses this issue.
<edward.yakop@xxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/12/2006 09:05 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
"Equinox development mailing list"
Re: [equinox-dev] Bug in "Run As
A simple test could be:
1. Add eclipse 3.2.1 plugins folder as target platform
2. Add org.ops4j.pax.logging.api http://repository.ops4j.org/maven2/org/ops4j/pax/logging/api/0.9.4/api-0.9.4.jar
to the plugins folder.
3. Set up a run as eclipse application, and set the program to run:
4. In plugins tab folder include org.ops4j.pax.logging.api
5. In arguments tab, in program argument add
5. Click Apply
6. Click Run
That syntax should be fine. It tells the bootstrap code (in EclipseStarter)
to mark the bundle for persistent start and set its start-level to the
value specified by the property osgi.bundles.defaultStartLevel
So we thought...
At the console run the "sl" command to see what start-level the
framework is set to and then run the "sl <bundle id>" command
to see what start level your bundle is set to. It seems like your
bundles have a start-level that is higher than the current start-level
of the framework. There are two properties you should pay attention
osgi.bundles.defaultStartLevel - used to set the start-level of installed
bundles that do not specify a particular start-level in the osgi.bundles
list (defaults to 4).
osgi.startLevel - used to set the initial start-level of the framework
(defaults to 6).
Yes, of course, we will double, double check that... I just got a queesy
feeling that bundle default startlevel and framework startlevel was mixed
If you set osgi.bundles.defaultStartLevel > osgi.startLevel then your
bundles will not be able to start because they will have a higher start-level
than the current Framework start-level. If this is not what is going
on then please open a bug against PDE-UI.