Thanks Daniel - works a treat:
- Daniel wrote :
Looks like Ant doesn't do the expansion that the shell does. This is OK
- I don't think it is supposed to. You can use the "apply" task and
specify the *.gz files as a fileset:
- Daniel
Euan Guttridge wrote:
>Hi
>
>Can
--- Christoph Bugel <[EMAIL PROTECTED]> wrote:
> IIRC you can also supply the args separately,
> instead
> of using line=.
>
s/can/should/
-Matt
>
>
__
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://person
If you want shell expansion, you could probably exec "sh" and use
On Wed, Apr 06, 2005 at 15:42:21 +0300, Daniel Blaukopf wrote:
> Looks like Ant doesn't do the expansion that the shell does. This is OK
> - I don't think it is supposed to. You can use the "apply" task and
> specify the *.gz file
Looks like Ant doesn't do the expansion that the shell does. This is OK
- I don't think it is supposed to. You can use the "apply" task and
specify the *.gz files as a fileset:
- Daniel
Euan Guttridge wrote:
Hi
Can anyone advise why the following works on the command line, but
> Can anyone advise why the following works on the command line, but not
> within an ant script. The error is 'file/directory does not exist', when
> it clearly does. If I change the *.gz to a specific file it works fine.
>
>
>
>
>
When you replace "rsync" with "echo" you will see that the
quo
Hi
Can anyone advise why the following works on the command line, but not
within an ant script. The error is 'file/directory does not exist', when it
clearly does. If I change the *.gz to a specific file it works fine.
Thanks
-
