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 22:08:04 UTC

[jira] [Commented] (SLING-6887) Remove commons.json and org.json from trunk

    [ https://issues.apache.org/jira/browse/SLING-6887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035509#comment-16035509 ] 

Karl Pauls commented on SLING-6887:
-----------------------------------

I think I'm almost done. The last thing that needs doing is the org.apache.sling.jcr.js.nodetypes (SLING-6901). Otherwise, all usage of org.json and commons.json is gone from trunk (except some minor bundle references in tests that we can ignore for now). As the nodetypes would be a lot of work and I'm not sure they are still developed I'll ask on the dev list if we can retire them first.

> Remove commons.json and org.json from trunk
> -------------------------------------------
>
>                 Key: SLING-6887
>                 URL: https://issues.apache.org/jira/browse/SLING-6887
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>
> Following-up on SLING-6679 where we removed all usage of commons.json and org.json from launchpad relevant bundles we still have some work to do to remove commons.json and org.json from all of trunk. 
> This is the umbrella issue for getting this done. I'll create sub-issues for the affected bundles and will resolve this issue when they are commons.json/org.json free and released. 
> When this issue is closed we shouldn't have references to commons.json/org.json in trunk anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)