ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steele, Richard" <r...@steelezone.net>
Subject Re: Unexpected <augment> behavior
Date Mon, 02 Dec 2013 12:49:16 GMT
Confirmed: a target "ab" that antcalls a and b individually doesn't exhibit
the same problem.


On Mon, Dec 2, 2013 at 12:12 AM, Stefan Bodewig <bodewig@apache.org> wrote:

> On 2013-12-01, Steele, Richard wrote:
>
> > Thanks for the confirmation, I created bug #55831.
>
> Thanks.
>
> > I'm assuming this problem will also rear up with our (legacy build's
> > mis)use of <antcall>, so this is actually pretty critical for us.
>
> Actually, <antcall> might "fix" it for you as each <antcall> will set up
> a fresh instance of the <augment> RuntimeConfigurableWrapper and you are
> not running the same task instance twice.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
>

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