Hi all, I guess I'm "volunteering" to look into SLING-6536 "Replace JSON implementation derived from org.json code".
>From what I understand, the idea would be to add an @Deprecated to all classes in there and do one final release before the 1th of April while at the same time replacing all usages of it inside sling with an alternative. The reason I'm bringing this to dev@ is mainly to ask two questions namely, 1) Is the above the way to go (and assuming it is) 2) What should I try to replace it with (there is a lot of json libraries out there: somebody suggested johnzon.apache.org but I'm certainly willing to look into others). If we have consensus on 1) I would do the releases and if we figured out 2) I would try to come-up with patches switching to the new library for the individual components that use commons.json and create JIRA issues for them with the patch attached. WDYT? regards, Karl -- Karl Pauls [email protected]
