[GROOVY-7311] Groovysh Command Parsing Flexibility

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.4.0
• Component/s: Groovysh
• Assignee: Unassigned
• Reporter: Stephen Mallette
• Created: 19/Feb/15 10:57
• Updated: 22/Feb/15 06:53

Description

This issue was precipitated by this discussion on groovy-users:

http://groovy.329449.n5.nabble.com/groovysh-and-command-parsing-td5722719.html

To summarize, command parsing in groovysh changed as of 2.4.0 to allow posix-style processing of arguments. While this was a good new feature, anyone who had built custom commands that relied on the old simple, method of processing those arguments had breaks in their commands.

It was suggested in the above mentioned thread that one possibility for resolving this issue in a more general way for the future would be to allow a command to decide for itself how to process its own arguments. This approach would provide a greater degree of flexibility to the command system by not tying a command to any particular method for dealing with its arguments.