I think you've misunderstood what I intended the "build-all" task to mean.
I think you're right. I've misunderstood the problem. Now that I think
I do, I probably would have gone with <ac:if> <then> NFS... </then>
<else> SSH </else> </ac:if> wrapped in a <macrodef>. Something like:
macro deploy
attr server
attr deploy-type defaults to [EMAIL PROTECTED]
sequential
ac:if ... then NFS else SSH
In your properties file, you can have:
server1.ip = ...
server1.deploy-type = ssh
server2.ip = ...
server2.deploy-type = nfs
See, no <antcall> ;-)
I think the [EMAIL PROTECTED] default atrtibute value trick
works, but my Ant is getting rusty since I don't use it, so I may be
wrong...
<property file="$environment}.properties" />
Watch out, missing { above.
<taskdef name="svn" classname="org.tigris.subversion.svnant.SvnTask" />
<taskdef resource="net/sf/antcontrib/antcontrib.properties" />
I'd advise you to use xmlns:ac="antlib:net.sf.antcontrib", which
disambiguate where tasks are coming from (<ac:for> instead of <for>,
etc...)
I hope this helps. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
