accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Findeisen (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4703) Attempt to pull all dependencies to latest version
Date Fri, 29 Sep 2017 07:16:06 GMT


Piotr Findeisen commented on ACCUMULO-4703:

This issue apparently started as a solution to my request to do something with Guava dependency,
which impacts end-users because Guava is not backwards compatible and Accumulo, while using
beta APIs, is not on the latest version (not even close so).

While pulling all dependencies to latest versions is the good thing to do, it it also time
consuming, as you have already realized, so _all dependencies_ will take much more time than
_1 Guava dependency_. At the same time ACCUMULO-4701 was rejected and ACCUMULO-4702 looks

*Would you consider starting with Guava* first, doing it on 1.7 and 1.8 branches as well,
_making a release_ and then continuing the effort for other dependencies?

> Attempt to pull all dependencies to latest version
> --------------------------------------------------
>                 Key: ACCUMULO-4703
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>            Assignee: Michael Miller
>            Priority: Blocker
>             Fix For: 2.0.0
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> This is issue is motivated by discussion in ACCUMULO-4701.   For 2.0.0 we should attempt
to use the latest version of any direct dependencies.   Not doing so may force user to use
older versions of dependencies with bugs and security problems. 
> ACCUMULO-4701 provides an example of this where Accumulo using methods that exist in
an older version of Guava but are dropped in a new version prevent a user from using newer

This message was sent by Atlassian JIRA

View raw message