[
https://issues.apache.org/jira/browse/ACCUMULO-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186370#comment-16186370
]
Christopher Tubbs commented on ACCUMULO-4703:
---------------------------------------------
[~findepi], the issue you saw will be fixed in the 1.7.4 and 1.8.2, as soon as
we release, which hopefully will be soon. There's no longer any issue affecting
our code like what you saw (as far as we can tell), but we'd like to take extra
steps to prevent such things in the future, if possible. That's what the
remaining effort has been focused on. But, your issue should be fixed in the
next releases.
> 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: 1.5h
> 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)
