[
https://issues.apache.org/jira/browse/ACCUMULO-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186067#comment-16186067
]
Michael Miller commented on ACCUMULO-4703:
------------------------------------------
[~findepi] Please see the mailing list discussion about Guava dependecies:
https://lists.apache.org/thread.html/0d9db4c22795bb00cdb65aede00075e1b996834be5e72e693bf44ca8@%3Cdev.accumulo.apache.org%3E
In particular see my comment about Hadoop:
We are tied down to Guava 14 because of Hadoop. This is the work
around since we can't just update Guava. Previously, we had just avoided
using 14 code that wasn't around anymore. Which was OK until code was
deprecated after version 14 and then removed, like in the case with
ACCUMULO-4701.
> Attempt to pull all dependencies to latest version
> --------------------------------------------------
>
> Key: ACCUMULO-4703
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4703
> 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 Guava.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
