Am 14.11.12 08:13, schrieb 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
On Wed, Nov 14, 2012 at 11:34 AM, Tom Schindl
tom.schi...@bestsolution.atwrote:
Am 14.11.12 08:13, schrieb 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
Subject:Re: [equinox-dev] Equinox, PDE and packages from the
ExtensionClasspath (e.g. JavaFX)
Sent by:equinox-dev-boun...@eclipse.org
Fragment-Host: system.bundle; extension:=extclasspath
Would this extension:=extclasspath cause problems to other
OSGi
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
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
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
