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=21988>. 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=21988 Uptodate task presentation bug [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-07-30 12:18 ------- I agree BUT it's quiet difficult to follow the build process in this case and the other subtask of my <condition> (a <available>) write a good name. I paste the log to explain : [available] Found file: foo.jar [null] foo/bar.java omitted as foo.jar is up to date. This is the log of the script I wrote above. I think it isn't normal that i found a null in the log, i prefer found uptodate. As i think it isn't normal that the condition task doesn't log anythings on verbose mode (but it should be another bug declaration). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
