commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <>
Subject [jira] Commented: (CLI-197) boolean option in documentation is woorking oposite way documented
Date Fri, 11 Jun 2010 21:07:14 GMT


Emmanuel Bourg commented on CLI-197:

This isn't an error in the documentation but it might be more explicit: if stopAtNonOption
is true an unrecognized token stops the parsing and the remaining tokens are added as extra
arguments. If stopAtNonOption is false the parsing breaks with an exception.

"Stop" doesn't refer to the action of throwing an exception, it refers to the change of the
parser behavior.

> boolean option in documentation is woorking oposite way documented
> ------------------------------------------------------------------
>                 Key: CLI-197
>                 URL:
>             Project: Commons CLI
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Anders Larsson
>            Priority: Minor
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
> In documentation it says as follows:
> CommandLine parse(Options options,
>                   String[] arguments,
>                   boolean stopAtNonOption)
>                   throws ParseException
>         stopAtNonOption - specifies whether to continue parsing the arguments if a non
option is encountered. 
> The parser stops an throws Exception if "stopAtNonOption" is set to false (when I guess
it should be other way round), if I set boolean "true", the parser ignores unknown arguments
and continues without throwing Exception.

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

View raw message