felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-75) Improve bundle activator detection in Maven OSGi plugin
Date Wed, 07 Jun 2006 14:13:30 GMT
    [ http://issues.apache.org/jira/browse/FELIX-75?page=comments#action_12415147 ] 

Richard S. Hall commented on FELIX-75:

My original approach was to do as you suggest, i.e., use an empty activator. However, it appears
in the maven plugin that I cannot tell the difference between an empty <bundleActivator>
tag and a non-existent <bundleActivator> tag...they both simply return NULL.

Further, I guess since it is causing so many problems for people, the better default is to
have them explicitly say they want auto-detection rather than making it the default.

> Improve bundle activator detection in Maven OSGi plugin
> -------------------------------------------------------
>          Key: FELIX-75
>          URL: http://issues.apache.org/jira/browse/FELIX-75
>      Project: Felix
>         Type: Improvement

>   Components: Maven OSGi Plugin
>     Reporter: Richard S. Hall
>     Priority: Blocker

> Currently, the Maven OSGi plugin detects the bundle activator by simply checking the
byte code constant pool for any class that references org.osgi.framework.BundleActivator.
This check is too simplistic for cases where subclasses of BundleActivator are used or in
cases where the activator is imported from another bundle. The first case could be improved
by better byte code analysis, I am not sure about the latter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message