ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject AW: Interesting <ant/> behaviour
Date Wed, 11 Aug 2004 09:13:38 GMT
Nice comment - I added that to the manual :-)

Jan

> -----Urspr√ľngliche Nachricht-----
> Von: Stefan Bodewig [mailto:bodewig@apache.org]
> Gesendet am: Mittwoch, 11. August 2004 10:50
> An: user@ant.apache.org
> Cc: sebastian.ssmoller@gmx.net
> Betreff: Re: Interesting <ant/> behaviour
> 
> On Tue, 10 Aug 2004, sebastian ssmoller <sebastian.ssmoller@gmx.net>
> wrote:
> 
> > is this expected behaviour ?
> 
> Yes.
> 
> > Why ?
> 
> Nested <property> elements of <ant> and <param> elements of <antcall>
> essentially become equivalent to properties you define on the command
> line.  These are special properties and they will always get passed
> down, even through additional <*ant*> tasks with inheritall set to
> false.
> 
> > I thought setting "inheritall=false would not "forward" any property
> > to the new env...
> 
> It will forward all properties defined on the command line or defined
> by a <*ant*> task as nested element that invoked the current build
> file (and recursively higher up until we reach the initial build
> file).
> 
> Stefan
> 
> ---------------------------------------------------------------------
> 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