/show_bug.cgi?id=31007
[PATCH] [CLI] Default Values for Arguments at definition stage
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
/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
/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
/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
/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
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.
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
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
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
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:
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
11 matches
Mail list logo