You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2017/05/26 14:54:04 UTC

[jira] [Resolved] (BOOKKEEPER-1010) Bump up Guava version to 20.0

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enrico Olivelli resolved BOOKKEEPER-1010.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.5.0

Issue resolved by merging pull request 166
            [https://github.com/apache/bookkeeper/pull/166]

            {noformat}
            commit fd3331a2769a29c379ed63e21ed2dc3c0f85ba25
Author:     arvindkandhare <ar...@emc.com>
AuthorDate: Fri May 26 16:52:57 2017 +0200
Commit:     Enrico Olivelli <eo...@apache.org>
CommitDate: Fri May 26 16:52:57 2017 +0200

    BOOKKEEPER-1010: Moving Guava to 20.0
    
    This patch updates Guava to version 20.0 and shades it
    
    Author: arvindkandhare <ar...@emc.com>
    Author: eolivelli <eo...@apache.org>
    
    Reviewers: Sijie Guo, Enrico Olivelli
    
    Closes #166 from eolivelli/guava_version

            {noformat}
            

> Bump up Guava version to 20.0
> -----------------------------
>
>                 Key: BOOKKEEPER-1010
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1010
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Arvind Kandhare
>             Fix For: 4.5.0
>
>
> Currently bookkeeper is using Guava 13.0. Guava has moved forward and at version 20.0 there are some API changes.
> This becomes an issue if a project using Guava 20.0 tries to run bookie server inproc. Bumping the Guava version to 20.0 will fix that issue.



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