following  it looks that the best options are currently either GSON or Jackson. i think GSON has smaller footprint and is more compact, but both are good options.
another criteria for choosing is: do they publish their APIs following semantic versioning? otherwise we have the same dilemma as with guava. for jackson this is the case, see https://github.com/FasterXML/jackson/wiki/Jackson-Releases for gson i've not found a documentation, but it seems they follow it as well, have not checked in detail. stefan >-----Original Message----- >From: Robert Munteanu [mailto:rmunt...@adobe.com] >Sent: Monday, November 28, 2016 10:35 PM >To: firstname.lastname@example.org >Subject: New JSON library > >Hi, > >The JSON license has been moved to 'Category X'  which means that we >can no longer use the org.json library. This has been announced on the >legal@ mailing list, please see  for the complete picture. > >We have until 30 Apr 2017 to remove all dependencies and inclusions of >the org.json library. We may decide to do this earlier, of course. > >I think it's a good time to drive down the TEF  of Sling and move to > using a more mainstream JSON library. I don't have a strong opinion on >the replacement, but I added a couple of ideas at . > >Anyone with an opinion, do chime in :-) > >Thanks, > >Robert > > >: https://www.apache.org/legal/resolved#category-x >: https://lists.apache.org/thread.html/bb18f942ce7eb83c11438303c818b >885810fb76385979490366720d5@%3Clegal-discuss.apache.org%3E >: Technical Exoticity Factory - I made it up on the spot >: https://cwiki.apache.org/confluence/display/SLING/New+JSON+library