Hi
I like this approach.
As to replacement options: I'd go for Apache Johnzon. First it's Apache hence
eating our own dogfood. But more importantly, it is an implementation of the
standard javax.json API. I much prefer standard APIs over the fragmented JSON
API scene.
Regards
Felix
Von meine
While I think that it is a good idea in theory to remove our custom JSON
library, I don't think that is practical in the near term. So I think our
best course of action is a multistep process:
1) Rewrite org.apache.commons.json using
https://github.com/tdunning/open-json.
2) Select a new standard
following [4] 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
