On Mon, May 2, 2016 at 10:00 AM, Josh Elser <[email protected]> wrote:
> 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 > Yea exactly :) I think we are on the same page now. I've read that Elastic blog post and they came to basically the same conclusions. I have no problem building a shaded artifact myself, but that is impossible when the artifact is already shaded. Here is a thought on how to accomplish this without drastically changing the avatica artifact. 1. Add a avatica-commons artifact that isn't shaded (that is the same as the avatica artifact). 2. avatica-server to avatica-commons 3. Point avatica to avatica-commons and keep it shaded. Kevin Risden
