ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mitch Gitman" <>
Subject Re: Ant 1.7 doesn't like antcall with inheritrefs
Date Thu, 18 Dec 2008 04:47:51 GMT
Disregard this post. Turns out in the Ant target called by *antcall*, I was
using refid below, not torefid:
    <antcall target="..." inheritrefs="true">
      <reference refid="*srcref*" torefid="*destref*" />

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 <> wrote:

> 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 this warning arises has been
> invoked by the *antcall *task with inheritrefs="true". This is a perfectly
> legitimate case of passing references to a target where the references *have
> *been set, just not by that sub-build.
> I'm wondering now, is there any way to call *antcall *with
> inheritrefs="true" and *not *get this warning?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message