accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4703) Attempt to pull all dependencies to latest version
Date Thu, 28 Sep 2017 20:04:01 GMT

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

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

Hmm, interesting. So, we can't detect the unknown parameter programmatically anymore? Perhaps
we can detect it and display usage by querying the JCommander API for unknown args after it
parses them?

> 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