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/03/28 13:12:41 UTC

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json

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

Karl Pauls commented on SLING-6679:
-----------------------------------

I just commited implementations for all the subissues (with the exception of the caconfig.impl). I still need to do some clean-up and will start resolving them when I did so. 

For now, I put in the SNAPSHOT versions in launchpad and replaced what needed replacement (e.g., the webconsole). With that, we have a working launchpad (the launchpad/testing works for me) without org.json (I removed the geronimo bundle) and without commons.json. 

When I'm done with the clean-up and we think there are no other problems anymore (might be good to wait a bit for that) I will start releasing the affected bundles and update the SNAPSHOTs in the launchpad with released versions. 

> Replace usage of org.apache.sling.commons.json.* and org.json
> -------------------------------------------------------------
>
>                 Key: SLING-6679
>                 URL: https://issues.apache.org/jira/browse/SLING-6679
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>
> Following the deprecation of org.apache.sling.commons.json (SLING-6536) we need to replace its usage everywhere else (at least if we want to be able to release other modules that depend on it). 
> This is the umbrella issue for getting this done. The idea is to create sub-issues with patches for individual components, review the patches, and when all are done: close this issue. 
> General discussions and problems should go to this issue and specific ones on the sub-issue in question.



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