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 Thu, 25 May 2006 20:34:30 GMT
    [ http://issues.apache.org/jira/browse/FELIX-75?page=comments#action_12413301 ] 

John Conlon commented on FELIX-75:

The OSGi plugin is creating an invalid manifest for the org.osgi.core bundle, by declaring
a Bundle-Activator to be the Interface.

Manifest-Version: 1.0

Archiver-Version: Plexus Archiver

Created-By: Apache Maven

Built-By: jconlon

Build-Jdk: 1.5.0_06

Extension-Name: org.osgi.core

Implementation-Title: org.osgi.core

Implementation-Version: 0.8.0-SNAPSHOT

Bundle-Activator: org.osgi.framework.BundleActivator

Export-Package: org.osgi.service.packageadmin;specification-version=1.

 2, org.osgi.service.url;specification-version=1.0, org.osgi.service.s

 tartlevel;specification-version=1.0, org.osgi.service.permissionadmin

 ;specification-version=1.2, org.osgi.framework;specification-version=

 1.3, org.osgi.service.condpermadmin;specification-version=1.0

Bundle-Version: 0.8.0.SNAPSHOT

Bundle-Vendor: OSGi Alliance

Bundle-Category: osgi

Bundle-DocURL: http://www.osgi.org/

Bundle-Copyright: Copyright (c) OSGi Alliance (2000, 2005). All Rights


Bundle-Name: osgi.core

Bundle-Classpath: .

Bundle-Description: OSGi Service Platform Release 4 Core Interfaces an

 d Classes.

Bundle-SymbolicName: osgi.core

> 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: Minor

> 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