felix-dev mailing list archives

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

John Conlon commented on FELIX-75:
----------------------------------

Specifying autodetection with:
<bundleActivator>auto-detect</bundleActivator>  will require all the bundles now
without the bundleActivator element (those relying on auto detection) to be edited.

How about the opposite approach? Using an empty element. <bundleActivator/> to NOT auto
generate a bundle and NOT specify one either?

> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message