You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2006/06/07 13:51:30 UTC

[jira] Updated: (FELIX-75) Improve bundle activator detection in Maven OSGi plugin

     [ http://issues.apache.org/jira/browse/FELIX-75?page=all ]

Marcel Offermans updated FELIX-75:
----------------------------------

    Priority: Blocker  (was: Minor)

Changed the priority to blocker because the plugin tries to create a bundle activator line for every bundle now. This means that library bundles like org.osgi.core now get org.osgi.framework.BundleActivator as their bundle activator.

> 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