[
https://issues.apache.org/jira/browse/FELIX-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091414#comment-17091414
]
Carsten Ziegeler commented on FELIX-6267:
-----------------------------------------
Please do not use Jira issues to ask questions - questions should be asked on
the mailing list.
cm.json uses geronimo-json_1.1_spec, version 1.2 which has a Provide-Capability
header for JavaJSONP - so bnd automatically adds this as a requirement to the
manifest for cm.json.
So you need a provider for this capability, the Sling bundle is one way, using
your additional configuration is another one; I don't think that one way is
preferred over the other. If you have already everything on the classpath,
using the framework properties looks ok to me - if you don't then a bundle
which has correct metadata like the Sling one is a good solution, too
> Felix cm.json v1.0.2 could not start due to missing capability requirement
> (&(osgi.contract=JavaJSONP)(version=1.1.0))
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-6267
> URL: https://issues.apache.org/jira/browse/FELIX-6267
> Project: Felix
> Issue Type: Bug
> Reporter: Rakesh Kumar
> Priority: Major
>
> I have just upgraded to Felix cm.json to v1.0.2 and the bundle could not
> start due to newly introduced capability requirement.
> osgi.contract; (&(osgi.contract=JavaJSONP)(version=1.1.0))
>
> However, the bundle v1.0.0 was working without any issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
