[
https://issues.apache.org/jira/browse/DRILL-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680623#comment-14680623
]
Daniel Barclay (Drill) commented on DRILL-3617:
-----------------------------------------------
It's not yet clear which modules/packages to shade.
Trying to shade basically everything except Drill doesn't seem to work.
(Shading every package except {{org.apache.drill.**}} shades references to
external things like {{java.lang.Object}}. Trying to add exclusions isn't
feasible, because symptoms don't reliably point to the package that needs to be
excluded.)
Reducing that to trying to shade basically all packages from depended-on Maven
packages/modules/artifacts doesn't seem work either, and symptoms are similarly
unclear (for example, Protobuf code complains that a method that seems to exist
doesn't really exist).
We might need to identify the key packages that currently have, or are likely
to have, version conflicts, can shade only those.
> Apply "shading" to JDBC-all Jar file to avoid version conflicts
> ---------------------------------------------------------------
>
> Key: DRILL-3617
> URL: https://issues.apache.org/jira/browse/DRILL-3617
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Fix For: 1.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
