Replace JSON.org with GSON dependencies

Description

This may seem like a silly suggestion, but the JSON.org 'used for good and not evil' license causes quite a few headaches when using a product commercially. Lawyers don't seem to have the same sense of humor as the JSON.org developers, and tend to view that this is an impossible clause to have in a contract. I've replaced JSON.org with GSON in a few projects, and in others, I created a shim layer that had the same interfaces, but a different implementation using GSON.

Anyway, thankfully, this does not seem to affect the main engine, which is the part that I'm really interested in, but I figured I'd mention it just in case.

Assignee

Frederik Heremans

Reporter

Leonardo Martins

Labels

None

Components

Fix versions

Priority

Minor
Configure