[CLI-244] Non-existing option is not reported as a failure when it follows an option that accepts multiple values

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2
• Component/s: CLI-1.x

Environment

Java 7
Linux/Windows

• Assignee: Unassigned
• Reporter: Ivan C
• Created: 07/Feb/14 15:50
• Updated: 16/Feb/24 16:28

Description

If I define the following options:

        Option dest = OptionBuilder
                .withArgName("-d")
                .withDescription("Destination")
                .hasArg()
                .create("-d");
        dest.setRequired(true);
        Option filenames = OptionBuilder
                .withArgName("-f")
                .withDescription("Filenames; comma separated")
                .hasArgs()
                .withValueSeparator(',')
                .create("-f");

when I parse the following arguments

-d c:\development\test -f abc.txt -qa hello

rather than getting a ParseException, the code thinks abc.txt, -qa, hello are the values for the -f option.

Issue Links

• is blocked by: CLI-221 cli's with last option as list type values and have argument are not parsed correctly