Publish Rest5Client without Jackson dependency

[anbusampath]

Description

elasticsearch-rest5-client brings jackson 2 dependency on runtime. #1064 (comment). It would be great if the rest5-client kept as minimal dependency on with http components alone.

elasticsearch-rest-client also works this way.

[anbusampath]

Sniffier depends on Jackson.

[l-trotta]

Hello, thank you for bringing awareness to this! elasticsearch-rest-client and elasticsearch-rest-client-sniffer used to be 2 different component, while for rest5 we decided to merge them under the same artifact. Since that is the only usage for the jackson library, we''ll see if it can be avoided.

[anbusampath]

rest5 we decided to merge them under the same artifact

In #1064 (comment), I asked for possibility of publishing sniffer as separate jar. Because sniffer is optional feature. In our current setup we don't use it.

Since that is the only usage for the jackson library, we''ll see if it can be avoided.

If jackson can be avoided it will be great, to go ahead with single artifact.

[l-trotta]

hey @anbusampath, I checked whether it was possible to just remove the jackson dependency, but the amount of code needed to parse the json without library would make the sniffer class much more complex than needed. Would it be better if we used a more lightweight library instead of jackson, such as json-p?

[anbusampath]

Would it be better if we used a more lightweight library instead of jackson, such as json-p?

that works as well.

I am not sure how much of effort it will required to shade the required classes support sniffer feature, so no transitive dependency.