Note that the OSGi 4.3 spec introduces the concept of Require-Capability. Equinox has a pre implementation of this with the Eclipse-GenericRequire, which of course is not understood by Felix. As a result, Felix doesn't know that it's missing a requirement (so starts it) whilst Equinox 'obeys' the Eclipse specific header.
If your version of both Equinox and Felix supported the Require-Capability and this bundle used the Require-Capbility then you'd see the same behaviour in both places. Alex On 19 Aug 2011, at 13:28, Kirchev, Lazar wrote: > Hello, > > I was experimenting with some bundles on Equinox and Felix and I observed a > case when one and the same bundle would start on Felix, but not on Equinox. > The reason was a custom manifest header, Eclipse-GenericRequire. Since this > is Eclipse-specific header, Felix ignores it and starts the bundle, although > there is no bundle providing such capability. Equinox detects that no bundle > provides the capability and does not start the bundle. > > I was wondering doesn’t this represent an incompatibility between the OSGi > implementations? > > Regards, > Lazar > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
