[
http://issues.apache.org/jira/browse/FELIX-75?page=comments#action_12415129 ]
Richard S. Hall commented on FELIX-75:
--------------------------------------
Ok, I did a quick and dirty hack to remedy this issue for the time being. For
now, to trigger auto-detection of the bundle activator you must specify:
<bundleActivator>auto-detect</bundleActivator>
If this is not specified, then bundle activator auto-detection will not happen.
Verification of specified activators still works the same as before, if one is
specified it is verified.
I will let Marcel decide if the "blocker" priority on this issue should be
removed.
> 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
