DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27085>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27085 NTFTPEntryParser wrong parsing of timestamp 12:24 PM ------- Additional Comments From [EMAIL PROTECTED] 2004-03-10 03:13 ------- I think you're right; I think this is a bug in java, or at least an undocumented feature since the 0-11 requirement for Calendar.HOUR is not in the javadocs. I just attached a jython script demonstrating this. (Jython is great for testing java classes this way). The script creates a Calendar, clears it, then sets its fields one by one. After each set the internals of the Calendar are printed out. All looks well until getTime() is called, after which the internals are messed up. I will shortly commit a fix to this problem. The fix will replace the use of Calendar.HOUR with Calendar.HOUR_OF_DAY which is much more reliable. But I have to do all the work myself, which sort of defeats the whole purpose of Calendar. I wonder how long this has been around. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
