Uploaded image for project: 'Commons CLI'
  1. Commons CLI
  2. CLI-165

PosixParser keeps processing tokens after a non unrecognized long option

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 1.2
    • Component/s: Parser
    • Labels:
      None

      Description

      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:

      --zop -abfoo

      is interpreted as:

      --zop -a -b foo

      but the last token should remain unchanged.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            ebourg Emmanuel Bourg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development