If you need to connect to existing Eclipse extension points, such as writing Eclipse plugins which must integrate into the existing Eclipse plugins, then you will probably need to use the Eclipse extension registry model.
If you are doing anything else, use OSGi Services via the OSGi Declarative
That is a bit of a dramatic statement that can open a can of worms. The extension registry and the Eclipse platform model with its many extension points does what it does very well. If you are developing bundles that plugin to the Eclipse platform do not "feel bad" about using the right
Yes, the plugin.xml is a leftover of the early days. OSGi offers the far
superior mechanism of Declarative Services. I'd strongly recommend to
avoid the old extensions wherever possible.
Regards,
Jürgen.
Am 29/09/2021 um 14:23 schrieb Mickael Istria:
Right, plugin.xml is an Eclipse-specific
Right, plugin.xml is an Eclipse-specific format for extensibility, which is
not part of OSGi specification. Support for this "extension registry" of
plugin.xml files is part of the org.eclipse.equinox.registry bundle. I
believe it's totally possible for Equinox to work comforming to OSGi spec
Hi all!
I don't know if this the correct mailinglist so apologies in advance if I took
a wrong turn.
I'm currently looking at the OSGi specifications (Core and compendium) and
Eclipse Equinox and am wondering what the status of "plugin.xml" is. Is it part
of any OSGi specification? Or is a
