Sounds good. Cheers,
Antoine ----- Original Message ----- From: "Steve Cohen" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, September 02, 2003 8:52 PM Subject: RE: Timestamp attribute processing I appreciate what you are saying. What I did so far, and none of it has been submitted yet, was to code my task to accept either of the ISO8601 formats in DateUtils (yyyy-MM-ddThh:mm:ss or yyyy-MM-dd) if no format is specified by the user, OR if the user specifies a time format in the parameters to the <stcheckout> task, parse only against that single format (and not the defaults). While that may fit your definition of a slippery slope, I really don't think so since the only defaults are standards and anything non-standard must be specified by the user in the same task-invocation as the data being passed to the task. And the "nested exception handler from hell" is only two levels deep. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
