On Mon, 24 Mar 2003, Brett Wooldridge <[EMAIL PROTECTED]> wrote:
>I've encountered it on both 1.5.1 and 1.5.2.
OK, this is bad.
I'll try to investigate it later this week.
Stefan
Stefan,
I've encountered it on both 1.5.1 and 1.5.2. While I have the
head locally, my company is currently running 1.5.1.
-brett
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2003 4:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Dy
On Sun, 23 Mar 2003, Brett Wooldridge <[EMAIL PROTECTED]> wrote:
>Sorry for being slow getting back to you,
No problem at all.
>I was recovering from an illness.
Hope you are better now.
>Here are to two stack dumps I promised.
Thanks.
It looks as if is not working the way it is
!
(sending this from a freakin Exchange web-client, hope it doesnt screw up!)
Brett Wooldridge
IronGrid, Inc.
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Fri 3/21/2003 1:27 AM
To: [EMAIL PROTECTED]
Cc:
Subject:Re: Dynamic Configurator
On
On Thu, 20 Mar 2003, Brett Wooldridge <[EMAIL PROTECTED]> wrote:
> When I run ant, I see that createDynamicElement() gets
> called twice for the element, and further that
> setDynamicAttribute() gets called twice for someattr.
This certainly sounds like a bug. We don't call the attribute setter
it".equals(name)) {
return new JUnitTask();
}
}
Which if called twice, of course, results in two JUnitTask objects
being created.
-brett
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 12:52 PM
To: Ant Developers List
Ant Dev with java gives an example.
I used DynamicConfigurator to implement custom
conditions in bugzilla bug no : 17199
I did not have the problems you describe.
Peter
On Thursday 20 March 2003 18:45, Brett Wooldridge wrote:
> Hello list,
>I'm trying to use DynamicConfigurator and am having
On Thursday, March 20, 2003, at 01:45 PM, Brett Wooldridge wrote:
Further, mywrapper is being used inside of a parallel task
(it may not matter, but I'm trying to provide all data).
Wow, quite a complex scenario you have there - using real Ant tasks as
nested elements *and* w
