[SLING-6536] Deprecate JSON implementation derived from org.json code

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Commons JSON 2.0.18
• Fix Version/s: Commons JSON 2.0.20
• Component/s: Commons
• Assignee: Karl Pauls
• Reporter: Stefan Seifert
• Created: 21/Feb/17 08:34
• Updated: 22/Mar/17 08:58
• Resolved: 17/Mar/17 16:32

Description

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
• org.apache.sling.commons.json.http
• org.apache.sling.commons.json.io
• org.apache.sling.commons.json.util
• 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.

Issue Links

• is related to: SLING-6679 Replace usage of org.apache.sling.commons.json.* and org.json in launchpad relevant bundles