hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17908) Upgrade guava
Date Sat, 06 May 2017 03:24:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999239#comment-15999239
] 

stack commented on HBASE-17908:
-------------------------------

[~julianhyde] Thanks for the input boss. We looking to shade out guava in a prebuild step.
Will report back her....

> Upgrade guava
> -------------
>
>                 Key: HBASE-17908
>                 URL: https://issues.apache.org/jira/browse/HBASE-17908
>             Project: HBase
>          Issue Type: Sub-task
>          Components: dependencies
>            Reporter: Balazs Meszaros
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading guava
is always a hassle because it is not always backward compatible with itself.
> Currently I think there are to approaches:
> 1. Upgrade guava to the newest version (21.0) and shade it.
> 2. Upgrade guava to a version which does not break or builds (15.0).
> If we can update it, some dependencies should be removed: commons-collections, commons-codec,
...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message