Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Eclipse-LazyStart vs Bundle-ActivationPolicy
Eclipse-LazyStart vs Bundle-ActivationPolicy [message #122561] Sun, 14 December 2008 22:03 Go to next message
Eclipse UserFriend
Originally posted by: jmordax.terra.es

Hi, I was developing with Eclipse R3.4.1 and PDE by default, when
checking "Activate this plug-in when one of its classes is loaded",
added to MANIFEST.MF the field:

Bundle-ActivationPolicy: lazy

This worked fine with 3.4.x and 3.5. But when I tested the plug-ins with
3.2.x it failed with a NPE. After some investigation, the problem was
that 3.2 doesn't understand Bundle-ActivationPolicy field. And PDE in
3.2.x adds this other field instead:

Eclipse-LazyStart: true

I have been searching the docs to find why these two different fields
theoretically to do the same thing with no luck. Do you know of any
article related?

Finally, to have plug-ins compatible with previous versions like 3.2.x I
have both fields added to MANIFEST.MF. Does it make sense to you? Can I
have any problem in new releases because I am using two fileds
theoretically for the same thing?

Thanks in advance,

Chemi.
Re: Eclipse-LazyStart vs Bundle-ActivationPolicy [message #122573 is a reply to message #122561] Sun, 14 December 2008 22:11 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ekkehard.gentz-software.de

Chemi,

since OSGI R4.1 OSGI supports lazy start using

Bundle-ActivationPolicy: lazy

so it makes sense to use this now as default, because its official
OSGI where Eclipse-LazyStart: true was equinox-only.

if you have to be compatible to older versions there's no probem to have
both in your manifest.mf

ekke

Chemi schrieb:
> Hi, I was developing with Eclipse R3.4.1 and PDE by default, when
> checking "Activate this plug-in when one of its classes is loaded",
> added to MANIFEST.MF the field:
>
> Bundle-ActivationPolicy: lazy
>
> This worked fine with 3.4.x and 3.5. But when I tested the plug-ins with
> 3.2.x it failed with a NPE. After some investigation, the problem was
> that 3.2 doesn't understand Bundle-ActivationPolicy field. And PDE in
> 3.2.x adds this other field instead:
>
> Eclipse-LazyStart: true
>
> I have been searching the docs to find why these two different fields
> theoretically to do the same thing with no luck. Do you know of any
> article related?
>
> Finally, to have plug-ins compatible with previous versions like 3.2.x I
> have both fields added to MANIFEST.MF. Does it make sense to you? Can I
> have any problem in new releases because I am using two fileds
> theoretically for the same thing?
>
> Thanks in advance,
>
> Chemi.
Re: Eclipse-LazyStart vs Bundle-ActivationPolicy [message #122581 is a reply to message #122573] Sun, 14 December 2008 23:23 Go to previous message
Eclipse UserFriend
Originally posted by: jmordax.terra.es

Perfect, thanks for the information. That is exactly what I was looking
for...

ekke wrote:
> Chemi,
>
> since OSGI R4.1 OSGI supports lazy start using
>
> Bundle-ActivationPolicy: lazy
>
> so it makes sense to use this now as default, because its official
> OSGI where Eclipse-LazyStart: true was equinox-only.
>
> if you have to be compatible to older versions there's no probem to
> have both in your manifest.mf
>
> ekke
Previous Topic:Problem with Equinox p2 and About info?
Next Topic:Bundle-RequiredExecutionEnvironment property support
Goto Forum:
  


Current Time: Tue Mar 19 04:45:56 GMT 2024

Powered by FUDForum. Page generated in 0.02524 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top