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=9231>. 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=9231 P4Counter should not mutate properties ------- Additional Comments From [EMAIL PROTECTED] 2002-05-22 07:43 ------- Sorry for the delay on this response but I was out of net connection. I see no merit on Les argument about an external program changing the counter in the middle of the build. If that where the case, no matter how often one runs this task there is always the posibility the value will be wrong. The only limitation here is that if you run the task 10 times you would have to use either 10 different properties OR doit from within an <antcall> which resets the value when one goes out of the scope. With respect to Erik comment about backward compatibility, I just have to say that I hope committers were more strict one the assesment of contributed tasks and whether they follow the rules that were decided. Several times we have been at the same point where the answer is: "Ups, we did not notice before the release, too late now, we are screwed for life". And then Stefan has to come up with a complete new machinery for parameter properties just because of one misbehaved task. We dig ourselves deeper and deeper. For the ANT2 team, I hope that you guys will review these and other tasks and make them stick to the rules (whatever they are from ANT2) no backward compatibility argument there. In the mean time can someone please at least deprecate Project.setProperty(). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
