Re: [equinox-dev] Equinox, PDE and packages from the ExtensionClasspath (e.g. JavaFX)

2012-11-13 Thread BJ Hargrave
Fragment-Host: system.bundle; extension:=extclasspath Would this extension:=extclasspath cause problems to other OSGi-Implementations like e.g. felix? A compliant framework should reject this manifest since the standard directive does not specify a valid value. If you are thinking of

Re: [equinox-dev] Equinox, PDE and packages from the ExtensionClasspath (e.g. JavaFX)

2012-11-13 Thread Neil Bartlett
I agree with BJ that it would be better to use an Equinox-specific directive for this Equinox-specific functionality. I believe that Felix should work fine today with the following: Fragment-Host: system.bundle;x-appclasspath:=ext because it would ignore the unknown directive, and would

[equinox-dev] IP CQs waiting on your team

2012-11-13 Thread portal on behalf of emo
equinox-dev, IPZilla records show that one or more of the projects on which you are developer are in need of attention. The following CQs have been in the 'awaiting_project' status for over 3 weeks and need your team to take action. rt.equinox: 6484 Apache Felix Resolver -- checkintocvs,

Re: [equinox-dev] Equinox, PDE and packages from the ExtensionClasspath (e.g. JavaFX)

2012-11-13 Thread Gunnar Wagenknecht
Am 14.11.2012 01:30, schrieb Neil Bartlett: I really feel that the problem is in the launcher, so that's where it needs to be fixed, i.e. by setting the osgi.parentClassloader=app system property. I agree. So the wrong property is only used if the Equinox is launched using the binary