The availability of manifest. MF, plugin. XML, and activator in Plug-in development

1. plugin. xml

Manifest. MF describes the basic information of bundle, which is related to osgi.
Plugin. xml describes the extension and extension points in the bundle.
After eclipse3.1, if the plug-in does not have any extension point information, there may not be a plug-in. xml file. That is, a plug-in may not contain the plugin. xml file.

 

2. manifest. MF

Before eclipse3.1, the OGSI list information can be written in plugin. xml. Therefore, you can see in some plug-ins of older versions that there is no manifest. MF file.

The real reason is that it writes the manifest. MF information to plugin. xml. After eclipse3.1, osgi Information and Extension Information are separated into manifest. MF and plugin. xml.

 

3. bundleactivator class

Subclass: plugin and abstractuiplugin. This class will certainly exist in the plug-in. To be dispensable, it depends on whether you need to control the bundle lifecycle.

At the same time, the start and stop methods of this class are not recommended to add too much complexity.Code.