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: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
