[
https://issues.apache.org/jira/browse/SLING-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025977#comment-16025977
]
Carsten Ziegeler commented on SLING-6885:
-----------------------------------------
Looking at the usage of json in the install bundle, it comes down to
InstallationResult
which creates a one line json response. Either using println or embedding for
example the JSONWriter from the Felix utils bundle should do the trick
The json generated by the source bundle is more complicated, so embedding above
writer does the trick
> Tooling support bundles no longer work due to dependency on
> org.apache.sling.commons.json
> -----------------------------------------------------------------------------------------
>
> Key: SLING-6885
> URL: https://issues.apache.org/jira/browse/SLING-6885
> Project: Sling
> Issue Type: Bug
> Components: Tooling
> Affects Versions: Tooling Support Install 1.0.2, Tooling Support Source
> 1.0.2
> Reporter: Robert Munteanu
> Fix For: Tooling Support Install 1.0.4, Tooling Support Source
> 1.0.4
>
>
> When deployed, both of these bundles fail to resolve due to importing:
> {noformat}org.apache.sling.commons.json,version=[2.0,3)
> org.apache.sling.commons.json.io,version=[2.0,3){noformat}
> Without thinking too much about it, I would venture to say the simplest way
> to support both all versions of the Sling launchpad and other variants such
> as AEM is to embed a JSON parser in the bundles and use that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
