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=7529>. 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=7529 depend task can't handle nested/inner classes with closure="yes" ------- Additional Comments From [EMAIL PROTECTED] 2002-04-10 02:00 ------- > In any case I have added a tolerance of 100 milliseconds to the time check > between class files and files on the classpath. This allows your example to > work. Wait! Please! Please don't add such a...um...ugl^H^H^Hunreliable, unpredictable, and special-case hack to Ant. As soon as somebody's compilation takes longer than 100 ms between writing two class files, it won't work. Additionally, since timing varies, you're introducing random behavior that will be a bear (like a grizzly, not a koala :-) ) to debug. (Different runs would show different class-file deletion behavior.) If there's no volunteer time right now to figure out a reliable solution to the (apparent) problem, please leave it the way it was rather applying that problematic fix. (That partial fix that will hide the problem (for a while) and will take much longer to debug when the problem isn't fully hidden.) Actually, making the time delay configurable and documented (so people will know what's going on and can adjust the value their compilation and editing speeds) would be good, though I don't know how much effort that would be. I'll see if I can help think about what a good solution would be. (I'm not familiar with everything that's stored in a class file. Is there any compilation timestamp or other data that would be the same for different .class files written from the same .java file?) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
