[
https://issues.apache.org/jira/browse/FELIX-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schurman updated FELIX-4066:
-----------------------------------
Description:
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
was:
There appear to be 2 somewhat related issues regarding consuming blueprint
augmented bundles in OBR. Both stem from the generated manifest:
# when exporting a service bean with 2 or more interfaces, only the first is
exposed in the manifest
# 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
> 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), Manifest Generator (mangen),
> Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Andrew Schurman
>
> 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
