ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9675] - Custom tasks can be run in an unconfigured state
Date Fri, 07 Jun 2002 00:33:00 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9675>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9675

Custom tasks can be run in an unconfigured state

conor@cortexebusiness.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From conor@cortexebusiness.com.au  2002-06-07 00:32 -------
I've tracked this down to the maybeConfigure method in RuntimeConfigurable.
The statement
  attributes = null

means the RuntimeConfigurable cannot be reused. When the task is invalidated by
the second taskdef, the new instance needs to be configured from the same
RuntimeConfigurable.

I'm not sure of the motivation for setting to null and what other impacts not
setting it to null may have. Obviously the statement
  characters.setLength(0);
is also a problem.

Commenting these out allows your build to run OK.

It does not appear that the child list is nulled out though. Want to test with a
nested element?

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message