[
https://issues.apache.org/jira/browse/HBASE-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051862#comment-15051862
]
stack commented on HBASE-14963:
-------------------------------
How about shading (and upgrading) guava? Would that work? Guava has loads of
goodies in it but its problematic if bare on our classpath given it evolves so
quickly and everyone is stuck on a different incompatible version?
> Remove Guava dependency from HBase client code
> ----------------------------------------------
>
> Key: HBASE-14963
> URL: https://issues.apache.org/jira/browse/HBASE-14963
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Attachments: no-stopwatch.txt
>
>
> We ran into an issue where an application bundled its own Guava (and that
> happened to be in the classpath first) and HBase's MetaTableLocator threw an
> exception due to the fact that Stopwatch's constructor wasn't compatible...
> Might be better to not depend on Stopwatch at all in MetaTableLocator since
> the functionality is easily doable without.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
