It looks to me that any bundle that attempts to depend on the new org.apache.sling.commons.johnzon:1.2.0 artifact produces a manifest for the new bundle that now makes it not activate when deployed to the sling runtime.
I opened https://issues.apache.org/jira/browse/SLING-9218 for tracking the problem. Does anyone know of any bnd-maven-plugin tricks to merge instructions from the manifest of a bundle that is being wrapped or would that have to be merged manually? Alternatively, maybe there is a convenient way to adjust the BND instructions so I can depend on the org.apache.sling.commons.johnzon:1.2.0 artifact without requiring the osgi.contract=JavaJSONP capability in the manifest? Regards, -Eric
