ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rebhan, Gilbert" <>
Subject RE: Question re sshexec task
Date Mon, 19 Dec 2005 15:21:55 GMT

Hi, Rhino

-----Original Message-----
From: Rhino [] 
Sent: Monday, December 19, 2005 2:55 PM
To: Ant Users List
Subject: Re: Question re sshexec task

>Oh dear, this looks like it is going to be a lot more involved than
>using the sshexec and scp tasks....

for me the ant tasks for ssh/scp didn't work, so i had to go with exec.

it's the same as using exec on windows =

<exec dir="./bat" executable="cmd.exe" os="Windows 2000">
            <arg line="/c bla.bat"/>

only on unix.

>If I understand this example correctly, it appears that you are
>executing a script on the remote server so that the server uploads from
>PC; Ant is just telling the server to initiate the script. Or am I 

The flow in short terms without all the details =

ant script on windows box packs all the stuff that should be deployed
to runtime environment (lying on several unix nodes) in n or more

transfer via ftp to one specific unix box, login @ that box and starting

that workflow will be even better in future, when ssh and scp work
directly from windows box
to unix, so that no ftp or login is needed anymore.
on windows i'll use the putty command line tools (plink ...) for that

there's only one antscript called on one unix box which does all the
work on n 
remote unix boxes via exec and ssh/scp.

No magic in it ;-)

>Hmmm. I may just do something similar. I can write a script in WinScp3
>grab whatever files I want to send to the server and run it on the
>Then, with a bit of luck, I can coax Ant to initiate that script for me
>that I don't have to start it manually.

Regards, Gilbert

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message