[
https://issues.apache.org/jira/browse/ACCUMULO-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184786#comment-16184786
]
Michael Miller commented on ACCUMULO-4703:
------------------------------------------
We are detecting unknown parameters through our use of the main parameter
defined as unrecognizedOptions. I guess we lucked out that we designed it that
way. I don't believe we will ever see this exception anymore though:
https://github.com/apache/accumulo/blob/master/shell/src/main/java/org/apache/accumulo/shell/Shell.java#L273
The exact behavior of JCommander acceptUnknownOptions is unclear though as I
noted here: https://github.com/cbeust/jcommander/issues/365
> 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)
