Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 81494 invoked from network); 25 Jul 2007 10:04:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jul 2007 10:04:46 -0000 Received: (qmail 16058 invoked by uid 500); 25 Jul 2007 10:04:42 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 15964 invoked by uid 500); 25 Jul 2007 10:04:42 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 15953 invoked by uid 99); 25 Jul 2007 10:04:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 03:04:42 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=NO_REAL_NAME,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of cknell@onebox.com designates 69.25.242.15 as permitted sender) Received: from [69.25.242.15] (HELO securemail.onebox.com) (69.25.242.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 03:04:40 -0700 Received: from outgoing.onebox.com (unverified [172.21.6.73]) by securemail.onebox.com (Rockliffe SMTPRA 7.0.6) with SMTP id for ; Wed, 25 Jul 2007 06:04:19 -0400 Message-ID: From: cknell@onebox.com To: user@ant.apache.org Subject: RE: Re: How can I capture a file's date to a property? Date: Wed, 25 Jul 2007 06:04:18 -0400 Content-Type: text/plain; charset="iso-8859-1" X-Virus-Checked: Checked by ClamAV on apache.org Thanks again. -- Charles Knell cknell@onebox.com - email -----Original Message----- From: Dale Anson Sent: Tue, 24 Jul 2007 20:13:41 -0600 To: Ant Users List Subject: Re: How can I capture a file's date to a property? What those mean is that there are other tasks or types with the same name loaded via one of the numerous jars in your ant classpath. You can make the messages go away by using namespaces, which then lets Ant explicitly pick the right task or type. Try it like this and the 'trying to override' messages will go away: timestamp on ant.jar is ${ant_date} This is a good thing to do when using third-party tasks, especially if they are from more than one source. It makes it a lot easier to figure out what task comes from where. Dale cknell@onebox.com wrote: > Thanks. That does it, but what's the story on this set of messages that are displayed when I run the task? > > Trying to override old definition of task antcallback > Trying to override old definition of task antfetch > Trying to override old definition of task assert > Trying to override old definition of task bool > Trying to override old definition of task foreach > Trying to override old definition of task if > Trying to override old definition of task limit > Trying to override old definition of task math > Trying to override old definition of task post > Trying to override old definition of task stopwatch > Trying to override old definition of task switch > Trying to override old definition of task var > Trying to override old definition of task replace > Trying to override old definition of task length > Trying to override old definition of datatype sort > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org