On Wed, 06 Apr 2005, Ninju Bohra wrote:
> [...]
> There have been efforts to integrate the "if" (and
> "unless") logic into all taskdefs, but it has been
> rejected repeatedly :-(
> [...]
Can anyone on this list tell me for what reason(s) the if/unless logic has
been rejected? Thanks.
Rainer, thanks for reminding me on . I forgot about it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mething like this:
>
>
> value="${basedir}/../..">
>
>
>
>
>
> Cheers,
>
> Rainer
>
> > -Original Message-
> > From: Holger Rauch [mailto:[EMAIL PROTECTED]
>
> > Sent: Wednesday, April 06, 2005 11:33 AM
> >
[EMAIL PROTECTED]
> Sent: Wednesday, April 06, 2005 11:33 AM
> To: user@ant.apache.org
> Subject: Overview on usage of if/unless attributes
>
>
> Hi!
>
> I'm aware that if/unless attributes can be used to select
> targets depending on whether the value of some prop
Hi!
I'm aware that if/unless attributes can be used to select targets depending
on whether the value of some property is set or not. Where else
(types/tasks) can if/unless be used in addition to targets?
Is there an overview on this issue in some place?
(I tried using "if" on in order to set th
