commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLI-9) CLI cant parse ANT option set as claimed in official usage guide
Date Tue, 15 Jun 2010 17:01:23 GMT

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

Emmanuel Bourg updated CLI-9:
-----------------------------

          Summary: CLI cant parse ANT option set as claimed in official usage guide  (was:
[cli] CLI cant parse ANT option set as claimed in official usage guide)
    Fix Version/s: 1.1
                       (was: 2.0)
      Component/s:     (was: CLI-2.x)

This was actually fixed in CLI 1.1 (related to CLI-14)

> CLI cant parse ANT option set as claimed in official usage guide
> ----------------------------------------------------------------
>
>                 Key: CLI-9
>                 URL: https://issues.apache.org/jira/browse/CLI-9
>             Project: Commons CLI
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ben Hutchison
>             Fix For: 1.1
>
>
> In the main usage guide to the CLI tool, it goes through a long example of how 
> to create the rules to parse the option set of ANT. Unfortunately:
> 1. If you follow the instructions given, the resultant parser with not be able 
> to parse the option set example given in the docs. The docs are simply wrong 
> and could not have been validated.
> 2. No matter what you do, the CLI software is too inflexible to *ever* parse 
> the ANT option set (How dumb is that??), because it insists that all options 
> that have a "-" prefix are one character long. 
> 3. The help formater doesnt work as documented on the usage page either - (due 
> to a bug it took just a minute to find) it only prints usage help for options 
> which have a single character descriptions, despite single char descriptions 
> not being mandatory.
> In all, Ive been extremely dissappointed and surprised that marginally tested 
> software of such poor quality and design, whose own scant docs blatantly dont 
> work as described, can make it into such a position of influence.
> I spent about an hour comparing the 3 OS Java command line parsing libs 
> yesterday, and (in part because of the (increasingly devalued) "Jakarta 
> Commons" brand) sadly it seems I put my money on the wrong horse.

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


Mime
View raw message