plugin.xml
) file. Plug-in descriptors are platform-defined objects that exist in the plug-in registry independent of whether a plug-in has been started. In contrast, a plug-in's runtime object (getPlugin
) generally runs plug-in-defined code.
This interface is not intended to be implemented by clients.
@deprecatedIPluginDescriptor
was refactored in Eclipse 3.0. Most of the functionality has moved to {@link Platform} and the plug-in descriptor has been replaced with the OSGi Bundle
object. This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in.
For most uses the bundle object can be treated as an opaque token representing your plug-in to the system -- It must be supplied to various Platform
methods but need not be interrogated itself. There are a small number of plug-in descriptor method equivalents supplied by Bundle
itself. The details are spelled out in the comments on each IPluginDescriptor
method.
Clients of this interface have a reference to an IPluginDescriptor
corresponding to a plug-in. To adapt to the deprecation, the bundle corresponding to the plug-in generally needs to be acquired. There are several cases:
IPluginRegistry.getPluginDescriptor()
. The code should be updated to use one of the bundle discovery mechanisms such as Platform.getBundle()
. The resulting bundle object can be used to carry out the adaptation steps outlined for each of the IPluginDescriptor
methods.
|
|
|
|
|
|