You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/09/30 14:48:15 UTC

DO NOT REPLY [Bug 23515] New: - really strange parsing behaviour

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23515>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23515

really strange parsing behaviour

           Summary: really strange parsing behaviour
           Product: Commons
           Version: 1.0 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: CLI
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: kpriblouda@yahoo.com


I'm just wondering, who came to glorious idea of storing parsed
option values on option object itself, while presence of those
options is stored on command line? 

My scenario: I have static class defining options I would like 
in several related command line applications.  

Sometimes I call those applications from "wrapper" - more than one
in a live of JVM, and then I fake differrent parameters. 

But cool feature of appending option values to array list inside option 
leads to very unexpected results...