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 Thu, 28 Sep 2017 19:47:00 GMT

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

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

I looked into the potential JCommander issue I mentioned above with versions after 1.60 and
I don't think it is a problem for us.  The only significant affect it has on our Shell is
that a single error message will be seen before the usage when a user enters an unknown parameter
on the command line.  Previous JCommander versions threw an exception which we had been eating
and simply printing usage.  

> 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 10m
>  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