[
https://issues.apache.org/jira/browse/SLING-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929897#comment-15929897
]
Konrad Windszus commented on SLING-6536:
----------------------------------------
Compare with the discussion at
http://www.mail-archive.com/dev@sling.apache.org/msg65534.html. Outcome was to
deprecate the full API and then no longer maintain this module. All consumers
have to use a different JSON library.
> Replace JSON implementation derived from org.json code
> ------------------------------------------------------
>
> Key: SLING-6536
> URL: https://issues.apache.org/jira/browse/SLING-6536
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons JSON 2.0.18
> Reporter: Stefan Seifert
> Assignee: Karl Pauls
> Priority: Critical
> Fix For: Commons JSON 2.1.0
>
>
> following the discussion in
> https://lists.apache.org/thread.html/ee51bace078681765d5dcfeda1939628ccefb9b4261b1d7f6a56d420@%3Cdev.sling.apache.org%3E
> we have to replace the implementation of all classes in Commons JSON that
> were derived from the original org.json code.
> the affected packages are
> *
> [org.apache.sling.commons.json|https://github.com/apache/sling/tree/trunk/bundles/commons/json/src/main/java/org/apache/sling/commons/json]
> *
> [org.apache.sling.commons.json.http|https://github.com/apache/sling/tree/trunk/bundles/commons/json/src/main/java/org/apache/sling/commons/json/http]
> *
> [org.apache.sling.commons.json.io|https://github.com/apache/sling/tree/trunk/bundles/commons/json/src/main/java/org/apache/sling/commons/json/io]
> *
> [org.apache.sling.commons.json.util|https://github.com/apache/sling/tree/trunk/bundles/commons/json/src/main/java/org/apache/sling/commons/json/util]
> *
> [org.apache.sling.commons.json.xml|https://github.com/apache/sling/tree/trunk/bundles/commons/json/src/main/java/org/apache/sling/commons/json/xml]
> unfortunately the unit test coverage for those packages is not very high. the
> main package has a line coverage of 42%, the other packages less than that or
> no at all.
> although we might encourage modules to switch to a standard JSON
> implementation a lot of modules inside sling and perhaps much more outside
> sling depend on this json implementation, so we should try to keep the
> exported API and functionality.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
