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 17883] - Custom task containers don't share property state across subtasks
Date Wed, 12 Mar 2003 14:58:18 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=17883>.
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=17883

Custom task containers don't share property state across subtasks





------- Additional Comments From dlwhiteman@us.ibm.com  2003-03-12 14:58 -------
So this was an intentional change in how things worked in TaskContainers 
between 1.4.1 and 1.5.2?  I didn't think you would want to break existing 
scripts.  I would think the default for custom tasks that implement 
TaskContainer would be that all subtasks are executed sequentially.  Note that 
my custom task isn't just a plain vanilla container; it does some other things -
 I just reduced it down to the simplest form to illustrate the problem

Mime
View raw message