Gson is used by Jest (our client for talking to Elasticsearch) internally.
So we could change our own JSON serialization routines to work with Jackson
or even plain StringBuilder if we liked (we took care to make the usage of
Gson an implementation detail), but the dependency to Gson would still b
I'm wondering why the Elasticsearch client for Hibernate Search is
using Gson, and not Jackson as JSON codec?
Especially as we already have Jackson as a dependency for both Search
(via Avro), OGM (via Couchbase), and it's also used within WildFly and
Camel, we might need to change this.
Sorry if
