Return-Path: <holtdl@yahoo.com>
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 3299 invoked from network); 24 Oct 2000 17:54:21 -0000
Received: from web106.mail.yahoo.com (HELO web106.yahoomail.com)
 (205.180.60.73)
  by locus.apache.org with SMTP; 24 Oct 2000 17:54:21 -0000
Received: (qmail 1354 invoked by uid 60001); 24 Oct 2000 17:54:21 -0000
Message-ID: <20001024175421.1353.qmail@web106.yahoomail.com>
Received: from [64.163.67.114] by web106.yahoomail.com;
 Tue, 24 Oct 2000 10:54:21 PDT
Date: Tue, 24 Oct 2000 10:54:21 -0700 (PDT)
From: Diane Holt <holtdl@yahoo.com>
Subject: Re: Property propagation?
To: ant-user@jakarta.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

I might be too sleep-deprived to be answering this correctly, but I think
you should be including a nested <property> in your <ant> calls, in order
to pass to the "clean" target's "myprop" the value you want. Ie:
<ant antfile="test.xml" target="clean">
  <property name="myprop" value="${myprop}"/>
</ant>

Diane

--- Stuart Halloway <stu@develop.com> wrote:
> According to the docs, properties are propagated by the "ant" task, and
> override any "property" task settings.  I am not finding this to be the
> case, e.g.
> 
> <project name="test" default="all" basedir=".">
>   <target name="clean">
>     <property name="myprop" value="other" />
>     <echo message="clean ran, myprop=${myprop}"/>
>   </target>
>   <target name="compile">
>     <echo message="compile ran, myprop=${myprop}"/>
>   </target>
>   <target name="all">
>     <echo message="all ran, myprop=${myprop}"/>
>     <ant antfile="test.xml" target="clean"/>
>     <ant antfile="test.xml" target="compile"/>
>   </target>
> </project>
> 
> The idea of this project is that "all" depends on "clean" followed by
> "compile," BUT "compile" does not depend on "clean."  To make this work,
> I
> execute "clean" and "compile" as "ant" tasks under the "all" target.
> 
> Properties passed on the command line correctly propagate to the ant
> sub-tasks, but then the "property" task is able to change them.  So,
> with
> the command line
> 
> 	ant -buildfile=test.xml -Dmyprop=foo all
> 
> the "all" task correctly uses the value "foo" but the "clean" task uses
> the
> value "other."  As a workaround, I can pass the properties explicitly,
> like
> this:
> 
> <ant antfile="test.xml" target="clean">
>   <property name="myprop" value="${myprop}" />
> </ant>
> 
> Is this an ant bug, a stu bug, or a doc error?  :-)
> 
> Stuart Halloway
> DevelopMentor
> http://staff.develop.com/halloway
> 


=====
(holtdl@yahoo.com)



__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf!  It's FREE.
http://im.yahoo.com/