You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Brian Egge (JIRA)" <ji...@apache.org> on 2007/09/14 22:58:32 UTC
[jira] Commented: (CLI-148) arguments are interpreted as options
[ https://issues.apache.org/jira/browse/CLI-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527632 ]
Brian Egge commented on CLI-148:
--------------------------------
Hi Matt,
This is a limitation of the CLI 1.x parser, and I don't think it would be possible to fix without breaking a lot of existing code and test cases. However, there are a couple of work around.
1) Don't include a space between the option and the arg.
2) Enclose the arg in quotes
I've attached a test case showing examples of the above two methods.
> arguments are interpreted as options
> ------------------------------------
>
> Key: CLI-148
> URL: https://issues.apache.org/jira/browse/CLI-148
> Project: Commons CLI
> Issue Type: Bug
> Components: CLI-1.x
> Affects Versions: 1.1
> Environment: Debian stable x86 with Sun JDK 1.6.0_02
> Reporter: Matt Ray
> Priority: Minor
>
> related to https://issues.apache.org/jira/browse/CLI-71
> The command-line parser interprets arguments to options as options if they match existing options. Example:
> Assume
> -a arg
> -b arg
> -a b -b a was fixed in CLI-71, but
> -a "-b" returns
> Unable to parse command line: no argument for:a
> -a "-c" is OK if "-c" is not defined as an option.
> The option in my case was "-password" and their password happened to match one of the options.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.