I figured out a workaround that's weird but it's the ONLY thing that makes the 
properties global and accessible outside the task where the input is used.

<target name="one">
     <input message="Enter val:" addProperty="newProp" />
     <property name="newProp" value="${newProp}" />
</target>

This actually works! It takes the value of the property "newProp" from the 
input and places it into a global property of the same name. Weird. I think the 
fact that input's "addProperty" doesn't make it global is a bug, since there's 
only supposed to be global properties in Ant.



--- On Sat, 9/12/09, don rhummy <[email protected]> wrote:

> From: don rhummy <[email protected]>
> Subject: How add global property with input task?
> To: [email protected]
> Date: Saturday, September 12, 2009, 6:32 PM
> When I have an Input task with
> "addProperty", the property it creates is only valid within
> that one target. So if two targets are being called in the
> same build run, the property added by the input task in
> target "1" is not visible in target "2"!! How would I add it
> globally?
> 
> The below two examples BOTH have the property "newProp" as
> existing only in target "one":
> 
> EXAMPLE ONE
> ------------
> <target name="one">
>      <input message="Enter
> something:" addProperty="newProp" />
> </target
> 
> 
> <target name="two">
>      <!-- Should NOT be called
> -->
>      <input message="Enter
> something:" addProperty="newProp" />
> </target
> 
> //Command prompt call
> mycomp> ant one two
> 
> 
> EXAMPLE TWO
> ------------
> <target name="one">
>      <input message="Enter
> something:" addProperty="newProp" />
> </target
> 
> 
> <target name="two">
>      <!-- Should NOT be called
> -->
>      <input message="Enter
> something:" addProperty="newProp" />
> </target
> 
> <target name="three">
>      <antcall target="one" />
>      <antcall target="two" />
> </target
> 
> //Command prompt call
> mycomp> ant three
> 
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to