[
https://issues.apache.org/jira/browse/HBASE-22087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801863#comment-16801863
]
Sean Busbey commented on HBASE-22087:
-------------------------------------
I'll have to go read that guide and probably update it. the only artifacts in
Hadoop that I know to have been properly set up to be consumed by downstream in
the past are the trio of hadoop-client-api, hadoop-client-runtime, and
hadoop-client-minicluster. My guess is those other artifacts are things folks
have historically considered client facing or that someone in the project
believes should be client facing.
You are correct that most of HBase's current woes wrt Hadoop classpath leakage
is because we do not rely on the proper three downstream artifacts. The last
time I tried to move us to them we still had a bunch of references to
not-for-downstream stuff.
> Update LICENSE/shading for the latest Hadoop trunk
> --------------------------------------------------
>
> Key: HBASE-22087
> URL: https://issues.apache.org/jira/browse/HBASE-22087
> Project: HBase
> Issue Type: Bug
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
> Attachments: depcheck_hadoop33.log
>
>
> The following list of dependencies were added in Hadoop trunk (3.3.0) and
> HBase does not compile successfully:
> YARN-8778 added jline 3.9.0
> HADOOP-15775 added javax.activation
> HADOOP-15531 added org.apache.common.text (commons-text)
> HADOOP-15764 added dnsjava (org.xbill)
> Some of these are needed to support JDK9/10/11 in Hadoop.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
