[ 
https://issues.apache.org/jira/browse/CLI-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benedikt Ritter resolved CLI-252.
---------------------------------
    Resolution: Fixed
      Assignee: Benedikt Ritter

{code}
$ svn ci -m "CLI-252: LongOpt falsely detected as ambiguous. This closes #2 
from github. Thanks to Simon Harrer."
Sending        src/changes/changes.xml
Sending        src/main/java/org/apache/commons/cli/Options.java
Adding         src/test/java/org/apache/commons/cli/bug/BugCLI252Test.java
Transmitting file data ...
Committed revision 1684315.
{code}

Thank you!

> 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
>            Assignee: Benedikt Ritter
>             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)

Reply via email to