[
https://issues.apache.org/jira/browse/HBASE-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206451#comment-16206451
]
Sean Busbey commented on HBASE-19018:
-------------------------------------
Some additional context for bystanders: test dependencies aren't included
transitively. we rely on the hadoop-minicluster dependency for the mini
dfs/yarn/etc clusters. that dependency is just a pom that pulls in various bits
from across the hadoop project so that it will have those mini cluster
implementations. This involves pulling in a fair number of test-jars. Without a
bunch of archeological work on Hadoop's repo and jira it's hard to say if the
lack of bouncycastle in the set of dependencies is intentional or not. But with
only a failed use of an internal class to go on, we'll be hard pressed to
change it.
> Use of hadoop internals that require bouncycastle should declare bouncycastle
> dependency
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-19018
> URL: https://issues.apache.org/jira/browse/HBASE-19018
> Project: HBase
> Issue Type: Bug
> Components: dependencies, test
> Affects Versions: 2.0.0-alpha-3
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
>
> The tests for HBASE-15806 rely on a Hadoop internal class,
> {{KeyStoreTestUtil}}, which in turn relies on the Bouncycastle library for
> certificate generation.
> when building / running with Hadoop 2.7.1, we accidentally get a bouncycastle
> implementation via a transitive dependency of {{hadoop-minikdc}}. When
> attempting to run against Hadoop 3.0.0-alpha4 and 3.0.0-beta1 (and presumably
> future Hadoop 3.y releases), this bouncycastle jar is no longer pulled in and
> we fail with a CNFE.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
