You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/05/02 19:05:13 UTC
[jira] [Created] (CALCITE-1224) Provide non-shaded and shaded
variants of Avatica artifacts
Josh Elser created CALCITE-1224:
-----------------------------------
Summary: Provide non-shaded and shaded variants of Avatica artifacts
Key: CALCITE-1224
URL: https://issues.apache.org/jira/browse/CALCITE-1224
Project: Calcite
Issue Type: Improvement
Components: avatica
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: avatica-1.8.0
Kevin Risden started a discussion about problems he using Avatica in certain environments because of the shaded classes.
https://mail-archives.apache.org/mod_mbox/calcite-dev/201605.mbox/%3CCAJU9nmgcPU9XnFh7RtR%3D4eDZ1Qg25qO0j6xudd_%3Ds89VZ3P1Ag%40mail.gmail.com%3E
After talking it out, we can to the conclusion that providing three things for Avatica clients should be sufficient for users:
# Provide an avatica client artifact with all dependencies shaded (relocated, when possible)
# Provide an avatica client artifact with no dependencies shaded
# Provide an example project (e.g. documentatino) users can modify to construct their own Avatica client artifact with just the dependencies they desire.
We can't reasonably enumerate all permutations of what might be desired by users WRT dependency versions, but we can provide them the tools to create the artifacts they need for their unique environment/deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)