It depends what you want to achieve. If you want the activator to run lazily, only when a class is loaded from the bundle for some other reason (eg because it contributes an extension) then that is exactly what BAP:lazy does.
If you don't have that class loading trigger, then you will have to find a way to start the bundle non-lazily (in this case the BAP:lazy is not needed, but also doesn't hurt anything). Unfortunately in Eclipse it's very hard to actually start a bundle, because the platform doesn't want you to. Neil > On 7 Oct 2015, at 08:58, Lars Vogel <[email protected]> wrote: > > Hi, > > I have a plug-in with an activator. It also sets the > Bundle-ActivationPolicy: lazy policy set, even though it provides no > declarative services nor any others services. > > id State Bundle > 208 ACTIVE org.eclipse.ui.cheatsheets_3.4.200.N20151006-2000 > osgi> services 208 > "No registered services." > > Do I still have to set the Bundle-ActivationPolicy: lazy policy set? > The Activator is definitely used in the code. > > Best regards, Lars > > -- > Eclipse Platform UI and e4 project co-lead > CEO vogella GmbH > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (032) 221739404, Email: [email protected], Web: > http://www.vogella.com > _______________________________________________ > equinox-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
