accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4703) Attempt to pull all dependencies to latest version
Date Fri, 29 Sep 2017 16:55:00 GMT

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

Michael Miller commented on ACCUMULO-4703:
------------------------------------------

bq.  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?

I eliminated the use of Beta code in 1.7 branch so the next release should work with the latest
Guava.  The 1.8 branch is another story though and we are opening subsequent tickets to deal
with Guava for that branch.

> 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)

Mime
View raw message