[SLING-9218] Incomplete OSGi manifest for Commons Johnzon 1.2.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons Johnzon 1.2.0
• Fix Version/s: Commons Johnzon 1.2.2
• Assignee: Konrad Windszus
• Reporter: Eric Norman
• Created: 18/Mar/20 22:07
• Updated: 27/Apr/20 16:14
• Resolved: 22/Apr/20 13:41

Description

It looks to me that any bundle that attempts to depend on the new org.apache.sling.commons.johnzon:1.2.0 bundle produces a manifest for the new bundle that makes it not activate when deployed to the sling runtime.
 
For example, the manifest now includes this instruction in the manifest:
 

Require-Capability: osgi.contract;osgi.contract=JavaJSONP;filter:="(&(
 osgi.contract=JavaJSONP)(version=1.1.0))",osgi.ee;filter:="(&(osgi.ee
 =JavaSE)(version=1.8))"

 
 
But it doesn't look like the org.apache.sling.commons.johnzon:1.2.0 manifest declares that it provides that JavaJSONP capability.
 
It appears that the equivalent "Provide-Capability" instruction is in the original org.apache.geronimo.specs.geronimo-json_1.1_spec artifact.  It contains the following in it's manifest but the o.a.s.commons.johnzon does not do the same when it wraps the bundle:
 

Provide-Capability: osgi.contract;osgi.contract=JavaJSONP;uses:="javax
 .json,javax.json.spi,javax.json.stream";version:List<Version>="1.1,1.
 0"

 

 
Alternatively, maybe there is a convenient way to adjust the BND instructions so one can depend on the org.apache.sling.commons.johnzon:1.2.0 artifact without requiring the osgi.contract=JavaJSONP capability in the manifest?
 

Issue Links

• blocks: SLING-9362 Use Apache Felix cm.json for JSON handling