[
https://issues.apache.org/jira/browse/FELIX-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923034#action_12923034
]
Emily Jiang commented on FELIX-2532:
------------------------------------
The workaround for this is to add the bundle-symbolic-name and bundle-version
in the capability of the xml when you generae for the exported packages. Below
is an example:
<capability name="package">
<p n="package" v="test.b2"></p>
<p n="version" t="version" v="1.0.2"></p>
<p n="bundle-symbolic-name" v="test.b2"></p>
<p n="bundle-version" t="version" v="1.0.2"></p>
<p n="mandatory" v=""></p>
</capability>
> bundle-symbolic-name constraint is not handled by the OBR resolver
> ------------------------------------------------------------------
>
> Key: FELIX-2532
> URL: https://issues.apache.org/jira/browse/FELIX-2532
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Affects Versions: bundlerepository-1.6.4
> Reporter: Arjun Panday
> Priority: Critical
> Attachments: DataModelHelperImpl.java
>
>
> I have a bundle importing javax.xml.bind specifically from the system.bundle.
> The import looks like this:
> Import-Package: javax.xml.bind;bundle-symbolic-name=system.bundle
> Bindex translates the import into the following requirement:
> <require extend='false'
> filter='(&(package=javax.xml.bind)(version>=0.0.0)(bundle-symbolic-name=system.bundle)(mandatory:<*bundle-symbolic-name))'
> multiple='false' name='package' optional='false'>
> Import package javax.xml.bind
> </require>
> This requirement is not resolved by the RepositoryAdmin service.
> When I loop over resolver.getUnsatisfiedRequirements(), I log:
> Unsatisfied OBR requirement
> (&(package=javax.xml.bind)(bundle-symbolic-name=system.bundle)(mandatory:<*bundle-symbolic-name))
> It seems that the bundle-symbolic-name constraint is not handled by the
> resolver.
> /arjun
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.