Return-Path: 
 <dev-return-50196-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 96364 invoked from network); 2 Sep 2003 19:54:25 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 2 Sep 2003 19:54:25 -0000
Received: (qmail 90696 invoked by uid 500); 2 Sep 2003 19:53:44 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 90613 invoked by uid 500); 2 Sep 2003 19:53:43 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 90528 invoked from network); 2 Sep 2003 19:53:42 -0000
Received: from unknown (HELO relay.t-online-com.de) (62.156.147.74)
  by daedalus.apache.org with SMTP; 2 Sep 2003 19:53:42 -0000
Received: from DJ0X820J (p5080eea8.dip0.t-ipconnect.de [80.128.238.168])
	by relay.t-online-com.de (SMTPSVC(1.0.0.1)) with ESMTP id 62C3F150031
	for <dev@ant.apache.org>; Tue,  2 Sep 2003 21:50:20 +0200 (CEST)
Message-ID: <0fd301c3718c$21a04ea0$020200c0@DJ0X820J>
From: "Antoine Levy-Lambert" <antoine@antbuild.com>
To: "Ant Developers List" <dev@ant.apache.org>
References: <D466FBEAA19E7E408BE3FAAC6EEB5676023FF860@utah.ignitemedia.com>
Subject: Re: Timestamp attribute processing
Date: Tue, 2 Sep 2003 21:55:16 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Sounds good.

Cheers,

Antoine
----- Original Message ----- 
From: "Steve Cohen" <SCohen@sportvision.com>
To: "Ant Developers List" <dev@ant.apache.org>
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org