Thank you for your mail. Avaleo office is closed from December 23 to January 2 were we will address you request. If you have urgent requests it's possible to call the following persons: - From December 23th to December 27th (both days included) please call Niels Dyrnesli on +45 40741496. - From December 28th to January 1 (both days included) please call Anders Kofoed +4529442941 Kind regards Anders Kofoed Avaleo ApS
-----Original Message----- Reply-To: "Jakarta Commons Users List" <[email protected]> Date: Sat, 30 Dec 2006 22:41:49 +0100 From: Henryk Konsek <[EMAIL PROTECTED]> To: [email protected] Subject: [CLI] Option.setArgs and Option.setArgName issues > Hi. > I was wondering about two scenarios. The first one: > option.setArgs(2); > option.setArgName( "argName" ); > Which results in something like this when printing help: > -myoption <argName> > I can't code something like: > option.setArgs(2); > option.setArgName( 1, "argName1" ); > option.setArgName( 2, "argName2" ); > ...so I was wondering whether is there any way to achieve something like: > -myoption <argName1> <argName2> > The second issue I can't figure out is how to enforce checking of amount > of arguments for option. That is how to prevent situations in which user > passes too much arguments for option (for instance for option with two > arguments): > java -jar command.jar -myoption one two three > At this moment I can't even check it in the code after getOptionValues() > due to the fact that additional arguments are simply ignored. > I would be grateful for any suggestions. > Greetings. > -- > Henryk Konsek > http://hekonsek.blogspot.com > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
