You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Benedikt Ritter (JIRA)" <ji...@apache.org> on 2015/05/22 09:13:17 UTC
[jira] [Commented] (CLI-252) LongOpt falsely detected as ambiguous
[ https://issues.apache.org/jira/browse/CLI-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555724#comment-14555724 ]
Benedikt Ritter commented on CLI-252:
-------------------------------------
Thank you for the report. Patches welcome!
> LongOpt falsely detected as ambiguous
> -------------------------------------
>
> Key: CLI-252
> URL: https://issues.apache.org/jira/browse/CLI-252
> Project: Commons CLI
> Issue Type: Bug
> Components: Parser
> Affects Versions: 1.3
> Environment: Windows 7, JDK 1.8.0v45
> Reporter: Simon Harrer
> Fix For: 1.4
>
>
> Options options = new Options();
> options.addOption(Option.builder().longOpt("importToOpen").hasArg().argName("FILE").build());
> options.addOption(Option.builder("i").longOpt("import").hasArg().argName("FILE").build());
> Parsing "--import=FILE" is not possible since 1.3 as it throws a AmbiguousOptionException stating that it cannot decide whether import is import or importToOpen. In 1.2 this is not an issue.
> The root lies in the new DefaultParser which does a startsWith check internally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)