Kyle Adams [mailto:[EMAIL PROTECTED]] writes:
> Right now there exists a workaround to the problem of
> property scope. Using the Antcall task, you can override a
> property set in a "master" file, and pass that property on to
> a sub-build file. [...]
>
> For example:
> c:\dev\src\ant -Dproject.dir = com/gfs/common
>
> <ant dir="subproject" target="build">
> <property name="project.dir" value="${project.dir}/subproject"/>
> </ant>
>
> This can be used to modify a path as it gets passed down a
> build hierarchy. The antcall task can also be used to do the
> same thing with other targets in the same build file.
Ah. Good. I found this one works for single pathname-valued properties. Thank you..
Now, for part 2: How do you do something similar for <path> specifications?
Thanks!
--
Shankar.
