[GROOVY-1455] CliBuilder incorrectly handles unexpected options

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.2
• Environment: Ubuntu 6.06 LTS `Dapper Drake' + JDK1.5.0_06 + Groovy SVN 2006-08-10T17:44
• Assignee: Paul King
• Reporter: Dr. Russel Winder
• Created: 10/Aug/06 12:21
• Updated: 08/Apr/10 02:38
• Resolved: 08/Apr/10 02:38

Description

CliBuilder absorbs unexpected single character options. Testing indicates that this is a problem in org.apache.commons.cli.* not in CliBuilder. I guess we have to nag someone about this.

CliBuilder appears not to be getting the ParseException when an unknown multicharacter option is seen. org.apache.commons.cli.* is correctly generating a ParseException in Java code so the problem is with Groovy. The code appears to say that on any ParseException, CliBuilder will write the usage message. A test shows this happens for missing required options but it is not happening for unexpected options.

Issue Links

• is depended upon by: GROOVY-2214 clearly state the implicit variables used with groovy command -p -n and -a options