Re: Unix commads behaving different in Ant task

2006-05-08 Thread Scot P. Floess
I just double checked myself...to be sure... Yeah, if you do a find with an asterisk, it will be expanded... Its especially problematic if the directory from which you are issuing a find contains a file that meets expansion... Alexey N. Solofnenko wrote: At least on Cygwin, Bash does not exp

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Alexey N. Solofnenko
At least on Cygwin, Bash does not expand asterisk, if there are no matching files. I thought this is a new "standard" behaviour. - Alexey. Scot P. Floess wrote: No, bash is the same way... You have to really do a find \*.jar I was sorta wrong in what I was saying...find in this case is doin

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Scot P. Floess
No, bash is the same way... You have to really do a find \*.jar I was sorta wrong in what I was saying...find in this case is doing the expansion (in the case where one escapes the asterisk)... Dominique Devienne wrote: $ rm *.txt # be carefull to run this in some temp dir $ mkdir newdir $

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Scot P. Floess
Users List Subject: Re: Unix commads behaving different in Ant task That won't work as a shell expands the asterisk Anderson, Rob (Global Trade) wrote: Your usage of the find command is incorrect. To find all the jars in ./myDir you would run the following: Find ./

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Dominique Devienne
$ rm *.txt # be carefull to run this in some temp dir $ mkdir newdir $ touch newdir/something.txt newdir/anotherthing.txt newdir/yetanother.txt $ find ./ -name *.txt ./newdir/something.txt ./newdir/anotherthing.txt ./newdir/yetanother.txt It works as expected because the shell does not expand the

RE: Unix commads behaving different in Ant task

2006-05-08 Thread Matt Benson
e- > > From: Scot P. Floess > [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 08, 2006 10:26 AM > > To: Ant Users List > > Subject: Re: Unix commads behaving different in > Ant task > > > > That won't work as a shell expands the > asterisk >

RE: Unix commads behaving different in Ant task

2006-05-08 Thread Anderson, Rob (Global Trade)
, since it will be a cross platform solution. -Rob A > -Original Message- > From: Scot P. Floess [mailto:[EMAIL PROTECTED] > Sent: Monday, May 08, 2006 10:26 AM > To: Ant Users List > Subject: Re: Unix commads behaving different in Ant task > > That won't w

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Alexey N. Solofnenko
There are many ways to do that. I like this: File list:${fs} - Alexey. Venkat Kotu wrote: Hi, I have a situation where in I need to find all the .jar files in a directory and write it to a temp file. The command from the prompt is : find myDir/*

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Dominique Devienne
On 5/8/06, Scot P. Floess <[EMAIL PROTECTED]> wrote: That won't work as a shell expands the asterisk is not a shell, so there's no need to escape the asterisk, unless one uses vmlauncher="false" or use a shell in 'executable'. --DD Anderson, Rob (Global Trade) wrote: > Your usage of the

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Scot P. Floess
ssage- From: Venkat Kotu [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:42 AM To: user@ant.apache.org Subject: Unix commads behaving different in Ant task Hi, I have a situation where in I need to find all the .jar files in a directory and write it to a temp file. The co

RE: Unix commads behaving different in Ant task

2006-05-08 Thread Anderson, Rob (Global Trade)
2 AM > To: user@ant.apache.org > Subject: Unix commads behaving different in Ant task > > Hi, > > > > I have a situation where in I need to find all the .jar files > in a directory and write it to a temp file. > > > > The command from the prompt is

Re: Unix commads behaving different in Ant task

2006-05-08 Thread Scot P. Floess
008253 (Mo) www.lionbridge.com -Original Message- From: Venkat Kotu [mailto:[EMAIL PROTECTED] Sent: Saturday, May 06, 2006 12:12 AM To: user@ant.apache.org Subject: Unix commads behaving different in Ant task Hi, I have a situation where in I need to find all the .jar files in a dir

RE: Unix commads behaving different in Ant task

2006-05-08 Thread Meshram, Tushar
Extn. 7123 (O) +91-9867008253 (Mo) www.lionbridge.com -Original Message- From: Venkat Kotu [mailto:[EMAIL PROTECTED] Sent: Saturday, May 06, 2006 12:12 AM To: user@ant.apache.org Subject: Unix commads behaving different in Ant task Hi, I have a situation where in I need to find all

Re: Unix commads behaving different in Ant task

2006-05-05 Thread Ivan \"Rambius\" Ivanov
Hello, --- Venkat Kotu <[EMAIL PROTECTED]> wrote: > Hi, > > > > I have a situation where in I need to find all the > .jar files in a > directory and write it to a temp file. You can use a pure Ant solution using and : ${jar.files} > The command from the prompt is : find myDir/*.jar >

Unix commads behaving different in Ant task

2006-05-05 Thread Venkat Kotu
Hi, I have a situation where in I need to find all the .jar files in a directory and write it to a temp file. The command from the prompt is : find myDir/*.jar and it lists all the .jar files from myDir directory. The ant target defined for the purpose is: