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

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs commented on ACCUMULO-4703:
---------------------------------------------

[~milleruntime] I saw a change pushed to bump up the minimum maven version to 3.2.5. You should know that the reason I kept it at 3.0.5 is because that's what ships in CentOS 7, and I wanted to make sure builds worked on a relatively recent enterprise OS. We may want to revert that change. Or, maybe it's fine. I don't feel strongly about it, it's just a point of consideration you may not have thought about.

> 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: 0.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)