Support for using Jackson instead of Gson

Currently the ApnsPayloadBuilder uses Gson to create the content for the payload.

Is it possible to make the creation of payload pluggable via some kind of interface, or extract a base builder that would have common methods for the locations where the conversion to JSON is needed?

The reason why I am asking for this is due to the fact that I would like to try and use one JSON parsing library within our project and currently we use Jackson a lot.

I am also prepared to work on this if you are interested and would accept such a PR.

[filiphr]

Please excuse the long delay in getting back to this.

No problem.

Respectfully, if we still have Gson as a dependency, why does it matter if we’re using Gson or Jackson to generate the payload? Is the idea that you’d then add an exclude clause for Gson if you really, really didn’t want it?

Yes the idea was that you can explicitly exclude Gson if you don’t need it. However, it depends on the approach you’ll like to take.

Here are some options that I have in mind:

• Do not to include any library and have a manual way of crafting the payload in case none are present
• Request from users to include a library
• Add 2 new artifacts that would either include Gson or Jackson as a dependency. If you want full backwards compatibility you can just add a Jacskon one that would exclude Gson and add Jackson

[jchambers]

This is covered by #776.