If I followed correctly, it's not that alters scope, it's
that opens a new scope. And since it does not inherit
references by default, the reference passed in correctly is
lost thru the use of .
Actually I think it may be some subtle interaction between these.
- if I have a global reference
> From: Rob Walker [mailto:[EMAIL PROTECTED]
> >> Have you tried to distill down your builds to something simple
> >> enough that can be sent whole for troubleshooting?
> >
> In fact I didn't even get as far as this before I spotted it ...
>
> In my top level build.xml, my "vt.class.path" referenc
Antoine
Thanks for the reply.
Also, please let us know which version of ant you are using.
The bug report http://issues.apache.org/bugzilla/show_bug.cgi?id=21724
describes your problem.
It was detected in ant 1.5.3 and solved in ant 1.6.0
Ant 1.6.2
I think the version was noted in my original ema
Hello Rob,
Also, please let us know which version of ant you are using.
The bug report http://issues.apache.org/bugzilla/show_bug.cgi?id=21724
describes your problem.
It was detected in ant 1.5.3 and solved in ant 1.6.0
Also in in ant 1.6.3 (coming soon, beta already available), another bug
conc
> From: Rob Walker [mailto:[EMAIL PROTECTED]
>
> Our top level build.xml looks like this:
>
>
> ...
>
>
>
>
>
>
>
>
>
>
>
> ...
>
>
We've been an Ant user for several years, and overall think it's great.
But something we've never been able to get working properly is
inheritrefs, either now in 1.6.2 or any previous versions.
Our top level build.xml looks like this:
...
