sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.* and org.json
Date Fri, 31 Mar 2017 11:42:41 GMT

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

Carsten Ziegeler commented on SLING-6679:
-----------------------------------------

Sure, but with that argument we could also say if one bundle is using bundle Y, then let's
use Y all over the place :)
I would like to get a running Sling with as less bundles as possible; now I totally agree
that it doesn't make sense to replace the json library in servlets.get or the importer. But
for modules which just produce json to be consumed by a web console plugin I think it makes
more sense. I haven't looked at all of those modules, but maybe it just applies to one or
two of them; adapter being one.

> 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)

Mime
View raw message