Kevin Risden wrote:
Would your life have been better if we expected slf4j-api to be provided
and not shaded?
The reason I don't like just having slf4j-api provided is that then I can't
use just the avatica artifact when connecting a client. I need to go get
slf4j-api as well. I'm thinking about connecting clients like DbVisualizer
or SQuirreL SQL here.
Ok, so here's an interesting point :). You have two unique cases for
what you'd like, depending on what you're running.
I recently read this short blog post about elasticsearch and shading
https://www.elastic.co/blog/to-shade-or-not-to-shade
Ultimately, they recognized that what dependencies a user actually wants
is untenable to manage. They provided an example Maven project which
shows how to create your own shaded version of elasticsearch, overriding
dependencies that you want.
I think I'm leaning towards..
1) A fully-shaded avatica client jar
2) A non-shaded avatica client jar
2a) An example project which shows how you can build your own shaded
artifact for your own purposes
