DO NOT REPLY [Bug 31007] - [PATCH] [CLI] Default Values for Arguments at definition stage

2004-09-06 Thread bugzilla
/show_bug.cgi?id=31007 [PATCH] [CLI] Default Values for Arguments at definition stage [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED

DO NOT REPLY [Bug 31007] New: - [PATCH] [CLI] Default Values for Arguments at definition stage

2004-09-01 Thread bugzilla
/show_bug.cgi?id=31007 [PATCH] [CLI] Default Values for Arguments at definition stage Summary: [PATCH] [CLI] Default Values for Arguments at definition stage Product: Commons Version: 2.0 Beta 1 Platform: Other OS/Version: Other

DO NOT REPLY [Bug 31007] - [PATCH] [CLI] Default Values for Arguments at definition stage

2004-09-01 Thread bugzilla
/show_bug.cgi?id=31007 [PATCH] [CLI] Default Values for Arguments at definition stage --- Additional Comments From [EMAIL PROTECTED] 2004-09-02 00:10 --- Created an attachment (id=12598) WriteableCommandLine interface added new method

DO NOT REPLY [Bug 31007] - [PATCH] [CLI] Default Values for Arguments at definition stage

2004-09-01 Thread bugzilla
/show_bug.cgi?id=31007 [PATCH] [CLI] Default Values for Arguments at definition stage --- Additional Comments From [EMAIL PROTECTED] 2004-09-02 00:10 --- Created an attachment (id=12599) WriteableCommandLineImpl

DO NOT REPLY [Bug 31007] - [PATCH] [CLI] Default Values for Arguments at definition stage

2004-09-01 Thread bugzilla
/show_bug.cgi?id=31007 [PATCH] [CLI] Default Values for Arguments at definition stage --- Additional Comments From [EMAIL PROTECTED] 2004-09-02 00:10 --- Created an attachment (id=12600) ArgumentImp - To unsubscribe, e-mail

Re: [CLI] default values

2004-02-17 Thread Rob Oxspring
Rob Oxspring wrote: Thats all good then. Hopefully tonight I'll play with a little code rather than just plot. First up will be moving logic from CommandLineImpl to a new WriteableCommandLineImpl so that CommandLineImpl can be used as a simple base for other CommandLine implementations.

Re: [CLI] default values

2004-02-16 Thread Rob Oxspring
John Keyes wrote: One of the failing unit tests on the ROXSPRING branch was the testWithOption method on CommandLineDefaultsTests. The reason it failed was the default value set during Option construction was not accessible to CommandLine.getValue. So to make this information accessible I

Re: [CLI] default values

2004-02-16 Thread John Keyes
Rob Oxspring wrote: John Keyes wrote: One of the failing unit tests on the ROXSPRING branch was the testWithOption method on CommandLineDefaultsTests. The reason it failed was the default value set during Option construction was not accessible to CommandLine.getValue. So to make this

[CLI] default values

2004-02-15 Thread John Keyes
One of the failing unit tests on the ROXSPRING branch was the testWithOption method on CommandLineDefaultsTests. The reason it failed was the default value set during Option construction was not accessible to CommandLine.getValue. So to make this information accessible I propose we add a

[cli] default values for arguments?

2002-06-10 Thread dion
I'd like to see a way of providing default values for options if the option is not present. Would this be a useful feature for others? I'm happy to do the work. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers:

Re: [cli] default values for arguments?

2002-06-10 Thread dion
to Jakarta Commons Developers List To: Jakarta Commons Developers List [EMAIL PROTECTED] cc: Subject:Re: [cli] default values for arguments? Check out the getOptionValue( char opt, String defaultValue) on CommandLine. If the option is not present