You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2017/06/02 21:37:04 UTC
[jira] [Resolved] (SLING-6885) Tooling support bundles no longer
work due to dependency on org.apache.sling.commons.json
[ https://issues.apache.org/jira/browse/SLING-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved SLING-6885.
-------------------------------
Resolution: Duplicate
Assignee: Karl Pauls
Sorry, didn't see this issue early enough. This work is done already (using the JSONWriter).
> 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
> Assignee: Karl Pauls
> 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)