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/22 16:06:41 UTC

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

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

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

I started to prototype some replacements and created sub-tasks for each. For now, the first 5 sub-tasks have patches that can be reviewed. SLING-6685 needs input as there is a question of what to do and SLING-6686 I'm unsure if needs to be changed. 

I will continue creating sub-tasks until I hopefully have all places that reference commons.json. However, it might be necessary to then start reviewing the places that depend on bundles that directly depended on commons.json because they might need to update version ranges.

> Replace usage of org.apache.sling.commons.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)