[ http://issues.apache.org/jira/browse/FELIX-75?page=comments#action_12415120 ]
Richard S. Hall commented on FELIX-75: -------------------------------------- Was there a patch that caused this new behavior? I didn't think so. I propose just removing activator detection altogether until a better approach can be found/implemented. If we everyone agrees, then I can do a quick hack to make it so. > 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
