[equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

2011-09-08 Thread Ben Cox
Hi All, We're being affected by a difference between Equinox 3.6.2 and 3.7, and can't quite work out whether it's caused by a bug fix, a bug being introduced, or a change in the OSGi spec from 4.2 to 4.3. Our code has been converted to use OSGi and runs purely on IBM JVMs, and as such has

Re: [equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

2011-09-08 Thread Thomas Watson
Subject:[equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7 Hi All, We're

Re: [equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

2011-09-08 Thread Alex Blewitt
See also the OSGi wiki page on http://wiki.osgi.org/wiki/Boot_Delegation Alex On Sep 8, 2011, at 13:42, Neil Bartlett wrote: Hi Ben, I tend to see this the other way around…. if you are using that package then you should have an Import-Package statement for it. If that causes problems for

Re: [equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

2011-09-08 Thread Ben Cox
Thanks, Tom, Neil, Alex. Tom, you got it! As you'd figured out, yes we are using the standard OSGi launcher, and adding osgi.compatibility.bootdelegation=true makes it work again. Thanks for the precise link to the bug report. Re Neil: looking back at this, I was actually surprised that it

Re: [equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

2011-09-08 Thread Neil Bartlett
Hi Ben, I don't use PDE any more, but I think as a workaround you should be able to create a system bundle fragment (i.e. Fragment-Host: system.bundle) to export the desired package(s). You may need to manually construct this outside of PDE and put it in your Target Platform, but once done it