[news.eclipse.tools.jdt] Re: Dot arguments expanded during launch

["Darin Wright" <Darin_Wright@xxxxxxxxxx>]

The replacements are file name expansions/matches in the working 
directory... i.e. files that start with "." (dot). I also tried other 
patterns and got the same behavior.

Darin

"Barry Lay" <blay@xxxxxxxxxxxxxxxxxxx> wrote in message 
news:f9r560$cc9$1@xxxxxxxxxxxxxxxxxxxx
>I am not sure what you mean by your answer.  When I run my sample program 
>from the DOS command line I get what I expect.  I don't know how DOS would 
>come up with such a creative set of replacements anyway.
>
> I am pretty sure this is Eclipse doing this as I originally found this in 
> a program that had the JET nature enabled.  In that case .jetproperties 
> showed up in the replaced parms as well.
>
> Barry
>
> Darin Wright wrote:
>> Well, this surpised me too... but it's not Eclispe - the same thing 
>> happens from the DOS command line. Using ".*" (i.e. quotes) worked from 
>> the command line, but not from Eclipse... not sure what the answer is 
>> yet.
>>
>> Darin Wright
>>
>> "Barry Lay" <blay@xxxxxxxxxxxxxxxxxxx> wrote in message 
>> news:f9l1jb$kbe$1@xxxxxxxxxxxxxxxxxxxx
>>> I have a program that expects a regular expression as part of its 
>>> command-line arguments.  When I tried putting ".*" in the Program 
>>> Arguments section of the Run Dialog, the program actually gets 
>>> ".classpath .project .settings" as arguments.  I can't find where this 
>>> behaviour is documented; all of the variables seem to be of the form 
>>> "${whatever}".
>>>
>>> Can this "feature" be disabled?
>>>
>>> I have seen this on both 3.2 and 3.3.
>>>
>>> Thanks.
>>