[jira] Resolved: (CLI-165) PosixParser keeps processing tokens after a non unrecognized long option

["Emmanuel Bourg (JIRA)" <ji...@apache.org>]

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

Emmanuel Bourg resolved CLI-165.
--------------------------------

    Resolution: Fixed

> PosixParser keeps processing tokens after a non unrecognized long option
> ------------------------------------------------------------------------
>
>                 Key: CLI-165
>                 URL: https://issues.apache.org/jira/browse/CLI-165
>             Project: Commons CLI
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: 1.1
>            Reporter: Emmanuel Bourg
>             Fix For: 1.2
>
>
> PosixParser keeps processing tokens after a non unrecognized long option when stopAtNonOption is enabled. The tokens after the unrecognized long option are burst, split around '=', etc.. instead of being kept as is.
> For example, with the options 'a' and 'b' defined, 'b' having an argument, the following command line:
> {code}--zop -abfoo{code}
> is interpreted as:
> {code}--zop -a -b foo{code}
> but the last token should remain unchanged.

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