Changes between Initial Version and Version 2 of Ticket #498


Ignore:
Timestamp:
21.08.2013 01:20:04 (9 years ago)
Author:
jri
Comment:

Core: fix DeepaMehta plugin detection (#498).

Plugin detection (is a particular OSGi bundle a DM plugin?) is based on inspecting the class hierarchy of the bundle's activator class.

Web application plugins (derived from WebActivatorPlugin?) are detected properly.

Close #498.

Changeset: cac81b32bd89513244aaf3c15fbba013fb7b6d5e

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #498

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
    • Property Summary changed from ALL_PLUGINS_ACTIVE event is fired more than once to DeepaMehta plugin detection fails sometimes
  • Ticket #498 – Description

    initial v2  
    1 This happens because the detection of DeepaMehta plugins (is a particular OSGi bundle a DM plugin?) is not accurate. This is the case when a plugin is not derived from PluginActivator directly but only indirectly. This in turn applies to web application plugins, which are derived from WebActivatorPlugin. 
     1Detection of DeepaMehta plugins (is a particular OSGi bundle a DM plugin?) is not accurate. This is the case when a plugin is not derived from PluginActivator directly but only indirectly. This applies e.g. to web application plugins, which are derived from WebActivatorPlugin. 
    22 
    33Currently DM plugin detection is based on inspection of a bundle's package imports. A solution would be to inspect the actual class hierarchy of the bundle's activator class.