groovy

Parsing of groovy(c) command-line arguments is too fragile

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.7-rc-2
  • Fix Version/s: None
  • Component/s: command line processing
  • Labels:
    None
  • Environment:
    Mac OS, Ubuntu
  • Number of attachments :
    0

Description

Tried to call 'groovy' with two command-line args: -c and -cp.

First, -cp isn't mentioned in the help (when typing 'groovy' alone).
Second, -cp must be given first, or a parsing error occurs. This sort of behavior is very hard to understand for a user (I had almost given up when I found this).

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. GROOVY-1525 "groovy -help" doesn't mention -cp option (also groovysh, groovyconsole etc.)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Roshan Dawrani added a comment -

Just wanted to add that support for -cp, -classpath options comes from startGroovy shell script, which is used by all command line programs - groovy shell, groovy console, groovyc, groovy, grape, etc. So, these options are available to all these programs but printed by none in their CLI help.

Inclusion of -cp, -classpath will need to be done in all of these.

Show
Roshan Dawrani added a comment - Just wanted to add that support for -cp, -classpath options comes from startGroovy shell script, which is used by all command line programs - groovy shell, groovy console, groovyc, groovy, grape, etc. So, these options are available to all these programs but printed by none in their CLI help. Inclusion of -cp, -classpath will need to be done in all of these.
Hide
Permalink
Roshan Dawrani added a comment -

Both unix and windows versions of startGroovy shell scripts seem to handle -cp, -classpath only if they are argument #1. May be, we should just document it in the CLI help that we put instead of trying to change the shell scripts and handle them at any position.

What do others think?

Show
Roshan Dawrani added a comment - Both unix and windows versions of startGroovy shell scripts seem to handle -cp, -classpath only if they are argument #1. May be, we should just document it in the CLI help that we put instead of trying to change the shell scripts and handle them at any position. What do others think?
Hide
Permalink
Paul King added a comment -

I think adding in a line into the CLI help is the way to go for the time being.
There is a header option we can use.

Show
Paul King added a comment - I think adding in a line into the CLI help is the way to go for the time being. There is a header option we can use.

People

  • Assignee:
    Unassigned
    Reporter:
    Peter Niederwieser
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: