Disregard this post. Turns out in the Ant target called by *antcall*, I was
using refid below, not torefid:
In other words, my mistake. And that warning was what was catching it. This
is one case where I'm happy to be embarrassed.
On Wed, Dec 17, 2008 at 8:41 PM, Mitch Gitman wr
I'm familiar with this warning in Ant 1.7:
Warning: Reference *reference_name* has not been set at runtime, but was
found during build file parsing, attempting to resolve. Future versions of
Ant may support referencing ids defined in non-executed targets.
But now suppose that the target in which t
