You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Piotr Findeisen (JIRA)" <ji...@apache.org> on 2017/10/20 12:28:00 UTC

[jira] [Commented] (ACCUMULO-4703) Attempt to pull all dependencies to latest version

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

Piotr Findeisen commented on ACCUMULO-4703:
-------------------------------------------

[~ctubbsii], do you have a release schedule for these versions?

> 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
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 2h 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)