aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1156) SPI-Fly static tool does not work with Require-Capability bundles
Date Mon, 10 Feb 2014 17:36:19 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896781#comment-13896781
] 

David Bosschaert commented on ARIES-1156:
-----------------------------------------

The syntax error with the manifest generation was fixed in http://svn.apache.org/viewvc?view=revision&revision=1566682

However there is one additional problem (exception on startup) which only appears when running
the statically woven bundle in combination with the org.apache.aries.spifly.static.bundle.
It does not appear when used with the dynamic bundle. 

I will look at that soon.

> SPI-Fly static tool does not work with Require-Capability bundles
> -----------------------------------------------------------------
>
>                 Key: ARIES-1156
>                 URL: https://issues.apache.org/jira/browse/ARIES-1156
>             Project: Aries
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> When processing the spi-fly-example-client2-bundle with the static tool, the bundle contains
invalid metadata and will not install. 
> Installation of the org.apache.aries.spifly.examples.client2.bundle-1.0.1-SNAPSHOT_spifly.jar
bundle in Equinox yields the following exception:
> Invalid manifest header Require-Capability: "osgi.serviceloader; filter:="(osgi.serviceloader=org.apache.aries.spifly.mysvc.SPIProvider)";cardinality:=multiple,"
> Note the trailing comma that should not be there.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message