ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles Scokart <gscok...@gmail.com>
Subject Re: <target>s unless/if: strangeness in default behaviour (imho) (ant 1.6.5)
Date Mon, 31 Aug 2009 18:12:42 GMT
You can write

<target name="t1">
    <property name="p"/>  <!-- Usualy not directly, but conditionaly or as a
potential side effect of some tasks -->
</target>


<target name="t" depends="t1" unless="p">
...
</target>





Gilles Scokart


2009/8/31 Francis GALIEGUE <fge@one2team.com>

> On Mon, Aug 31, 2009 at 12:59, Gilles Scokart<gscokart@gmail.com> wrote:
> > This is indeed as designed, and it is pretty usefull because you can set
> the
> > property p in t1 or t2.  This pattern is quiet often used.
> >
> >
>
> Does this mean that you can:
>
> <target name="t1" unless="p, p1"/>
>
> or:
>
> <target name="t1" unless="p" unless="p1"/>
>
> ?
>
> Maybe this pattern is often used, but as I said, it looks pretty much
> counterintuitive to my eyes. If a property is dependent on the
> (non)existence of a property and this property does/does not exist, I
> don't expect this target to be executed at all.
> --
>
> Francis Galiegue
> ONE2TEAM
> Ingénieur système
> Mob : +33 (0) 683 877 875
> Tel : +33 (0) 178 945 552
> fge@one2team.com
> 40 avenue Raymond Poincaré
> 75116 Paris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message