felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Schurman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-4066) Unable to load blueprint augmented jars with OBR
Date Thu, 27 Jun 2013 19:36:20 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Schurman updated FELIX-4066:

    Attachment: 1002-Refactor-blueprint-tests-into-multiple-tests.patch

I've attached a patch series that fixes (1). For (2), I don't like the idea of exporting a
comp-name for every service. We could remove the comp-name filter in order to support bundles
which may have been build with previous versions of felix. But I think it might be best in
these cases to manually add <service-properties/> to a blueprint file.

1 - Fixes the issue with minimal changes
2 - Refactors blueprint tests to make them more robust
> Unable to load blueprint augmented jars with OBR
> ------------------------------------------------
>                 Key: FELIX-4066
>                 URL: https://issues.apache.org/jira/browse/FELIX-4066
>             Project: Felix
>          Issue Type: Bug
>          Components: Bundle Repository (OBR), Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.7
>            Reporter: Andrew Schurman
>             Fix For: maven-bundle-plugin-future
>         Attachments: 1001-Export-all-service-interfaces-in-blueprint.patch, 1002-Refactor-blueprint-tests-into-multiple-tests.patch,
> There appear to be 2 somewhat related issues regarding consuming blueprint augmented
bundles in OBR. Both stem from the generated manifest:
> 1) when exporting a service bean with 2 or more interfaces, only the first is exposed
in the manifest
> 2) when importing a service via interface and component-name, you never find the service
as the component-name is never exposed on the exporting side

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message