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 Fri, 30 Jun 2017 11:55:00 GMT

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

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

Hmm... The tests pass locally for me. Can't repro the mvninstall compiles issues locally using
same commands.  Let me retry.

> 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
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17908.master.001.patch, HBASE-17908.master.002.patch, HBASE-17908.master.003.patch,
HBASE-17908.master.004.patch, HBASE-17908.master.005.patch, HBASE-17908.master.006.patch,
HBASE-17908.master.007.patch, HBASE-17908.master.008.patch, HBASE-17908.master.009.patch,
HBASE-17908.master.010.patch, HBASE-17908.master.011.patch, HBASE-17908.master.012.patch
>
>
> 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.4.14#64029)

Mime
View raw message