commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CLI-150) Negative numbers mistaken for options
Date Wed, 30 Jul 2008 20:21:31 GMT

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

Oliver Heger resolved CLI-150.
------------------------------

    Resolution: Fixed

Fix applied in revision 681191.

WriteableCommandLineImpl.looksLikeOption() now tries harder to find out whether an element
of the command line is an option. Instead of simply checking for a possible option prefix,
it now also verifies whether an option with such a name exists in the current group.

> Negative numbers mistaken for options
> -------------------------------------
>
>                 Key: CLI-150
>                 URL: https://issues.apache.org/jira/browse/CLI-150
>             Project: Commons CLI
>          Issue Type: Bug
>          Components: Parser
>         Environment: Sun JDK 1.6, Ubuntu 7.04
>            Reporter: Dioktos
>             Fix For: 2.0
>
>         Attachments: BugCLI150Test.java, patchCL150.patch
>
>
> If an option has a negative numerical argument, the parser mistakes it for another option
and throws an error. For example, consider:
> {{Argument numArg = aBuilder.withValidator(NumberValidator.getNumberInstance()).withMinimum(1).withMaximum(1).create();}}
> {{Option numOpt = oBuilder.withLongName("num").withArgument(numArg).create();}}
> {{Group options = gBuilder.withOption(numOpt).create();}}
> Then parsing {{--num -0.1}} results in:
> {{Unexpected -0.1 while processing --num}}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message