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 9190] - Task.setTaskType should be protected or public
Date Fri, 17 May 2002 03:54:32 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=9190>.
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=9190

Task.setTaskType should be protected or public





------- Additional Comments From conor@cortexebusiness.com.au  2002-05-17 03:54 -------
I agree - the field should be private. In fact all fields should be private.
Unfortunately this is not the case :-(. It cannot just be changed now due to
backward compatability considerations.

In fact one of the things Ant suffers from is that its API has not been well
controlled and many things are too open. This makes evolution harder, again due
to backward compatability issues. I hope this explains my initial reaction. 

Since the Task objects are being created by Ant's core (in the createTask
method) the core should be setting this value and it should not be something a
task should mess with. 

Can I ask you how you are using this field and what problems you are currently
seeing? By the time your task execute it should be set correctly.

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