----- Original Message -----
From: "Conor MacNeill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 06:30
Subject: Re: Ant2 Proposal
> Tim,
>
> ----- Original Message -----
> > What Conor appears to be suggesting in mutant (cool name BTW)
> > is more useful than that.
>
> Thanks, I'm experimenting with letting many aspects be remote. :-) I'm
> still playing with the possibilities. A remote installer for Ant,
> centralised build files, CJAN style access to jars on demand, who knows
> what else. What is useful, well probably only time will tell.
I'm actually using ant for final deploy of web apps; a different xml file
for each server (tomcat.xml, bluestone.xml... , each with the same set of
targets 'start-server', 'restart-server', install-files).
So the deploy task on the main box uploads the a zip file (ftp), then
remotely unzips it and hands off to the ant task at the far end, the tasks
deriving box specific details from env variables (TOMCAT_HOME) and
pre-installed property files.
<target name="install-test" depends="deploy-to-test">
<telnet userid="${testserver.user}" password="${testserver.password}"
server="${testserver.server}" timeout="30">
<read string=">"/>
<write string="cd ${dir.copy}"/>
<read string=">"/>
<write string="jar -xf package.zip"/>
<read string=">"/>
<write string="cd dist"/>
<read string=">"/>
<write string="ant -buildfile tomcat.xml"/>
<read string="dist>"/>
<write string="ant -buildfile asp.xml"/>
<read string=">"/>
</telnet>
</target>
This only works when the destination boxes are accessible via telnet/ftp. I
have had to use telnet to a unix box and then ssh from the command line of
that box to get things to work with a more secured destination.
Anyway; remote ant invocation does work and is usefal as an install
mechanism, today, it is just fiddly in places.
-Steve
ps, Did you know 'Mutant' is also the name for mutexes in the NT Kernel?
