Replicating Peter's proposal? Great!!!
Please do not forget to add if/unless/ifTrue/os/osfamily attributes please.
Also, would it work with ant-contrib's <if> (thus not requiring the
attributes mentioned above)? Like in:
<target name="foo">
<do-something />
<depends target="bar" />
<if>
<condition>
<istrue value="${bar-did-something}" />
</condition>
<then>
<depends target="baz" />
</then>
</if>
</target>
BTW, I find that having <isset property="x"/> and <istrue value="${x}"/> is
confusing, and the issue came up on the list at least once. Couldn't we have
simply a <istrue property="x"/> as well? --DD
-----Original Message-----
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 03, 2002 1:56 AM
To: Ant Users List
Subject: Re: Maintaining dependencies across antcalls
Laurie Harper wrote:
> Erm, yes, that's the point. I want to be able to declare my dependencies
> (for example, so that I can expect 'ant worker' to work as well as 'ant
> master') without getting required targets executed repeatedly.
Understand, you need an inner <depends target=""/> tag.
I've almost finished it (fixing a but), and will submit it soon, stay
tuned :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
