ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebastian ssmoller <>
Subject Interesting <ant/> behaviour
Date Tue, 10 Aug 2004 16:22:35 GMT
first: i am not subscribed to the list so please use "reply to all" or
add my private email addr to the cc list - thx.

i discovered the following interesting behaviour. i do not know whether
it is "defined"/expected or a bug so i decided to ask :)

i have two build scripts

----- a.xml -----
<project name="a">

    <property name="var" value="global"/>

    <target name="call">
        <ant antfile="b.xml" inheritall="false" target="echo"/>

    <target name="caller">
        <antcall target="call">
            <param name="var" value="UPS :("/>

----- a.xml -----

----- b.xml -----
<project name="b">

    <target name="echo">
        <echo message="something to say : ${var}"/>

----- b.xml -----

so know when i call:

$ ant -f a.xml call

i get the expected result that the ${var} is not evaluated but when i do

$ ant -f a.xml caller 

${var} evaluates to "UPS :(" 

is this expected behaviour ? Why ? I thought setting "inheritall=false
would not "forward" any property to the new env...


"Perfection is achieved, not when there is nothing left to add, 
but when there is nothing left to take away."  
--- Antoine de St. Exupery, Wind, Sand, and Stars, 1939 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message