[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-user
Subject:    Re: [groovy-user] Groovy argument handling in beta5 v beta6
From:       Jeremy Aston <jeremy.aston () realitylogic ! com>
Date:       2004-08-17 10:26:31
Message-ID: E8358757-F037-11D8-B810-000D93AD39A6 () realitylogic ! com
[Download RAW message or body]

mmm - I tried --p as well and that is still getting picked up by groovy.

jez

On 17 Aug 2004, at 11:20, Yuri Schimke wrote:

> We are parsing command line options now.  gnu long style.  But it's 
> strange its still parsing arguments after the first non option.
>
> I tried using -- (gnu standard for end of options).  But it seems like 
> its a bug in either GroovyMain or the getopt library.
>
> On 17/08/2004, at 1:07 PM, Jeremy Aston wrote:
>
>> Hi,
>>
>> I have recently moved from beta 5 to beta 6 on Mac OS X and some of 
>> my scripts have stopped working.  The ones that are affected are ones 
>> that pass arguments to the script in the form 
>> "-p/a/path/from/root/to/a/file"
>>
>> In Beta 5 I could have a line like:
>>
>> groovy -cp <classpath> MyScript.groovy -p/a/path/from/root/to/a/file
>>
>> Now with Beta 6 it appears that the "-p" is being picked up by the 
>> main groovy handler and attempting to be parsed resulting in the 
>> following error:
>>
>> error: Unrecognised option: -/
>>
>> My script was getting the args, testing for "-p" and stripping the 
>> path out for use in the script.  If I wrap the -p with different 
>> delimiters, say "[p]/a/path" it works fine (with the appropriate 
>> change to my args parsing routine of course).
>>
>> Has anyone else experienced this?  Am I being stupid or is there a 
>> solution for this?
>>
>> Many thanks
>>
>> Jeremy Aston
>>


[prev in list] [next in list] [prev in thread] [next in thread]