- there is a date selector with a method DateSelector#setDateTime which contains parsing code (with a hardcoded US locale, looks like the europeans (continentals) are not allowed to enter DD-MM-YYYY dates, MM-DD-YYYY is preferred.
- there is a DateUtils class in ant It has methods to format dates, but not to parse them. Parsing methods should be added there. - the cvstagdiff task has attributes which are date/timestamps, but the task does not parse these attributes itself, rather they are copied without parsing as command line arguments for the cvs executable. - the tstamp task can create strings (properties) representing dates, but does not have to parse the strings back Cheers, Antoine ----- Original Message ----- From: "Steve Cohen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 01, 2003 9:58 PM Subject: Timestamp attribute processing There have been some requests to add functionality to the stcheckout task (for StarTeam) to enable checkout by a timestamp. It will not be hard to do this, as the scenario is well-supported in the StarTeam API. However, what about the Ant API? Is there a standard way (and reusable/accessible code) for passing in timestamps as attributes to a task? It seems like a bad idea for every task to roll its own date-parse processing. Can someone point me at a better way to implement it in ant? Ideally this would support at least yyyy-MM-dd, yyyy-MM-dd hh:mm without making the user supply a date-format string. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
