Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 73675 invoked by uid 500); 25 Jul 2001 14:14:49 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 73663 invoked from network); 25 Jul 2001 14:14:48 -0000 Reply-To: From: "Kevin Cummings" To: Subject: RE: Trying FTP Again Date: Wed, 25 Jul 2001 09:05:24 -0500 Organization: Mongoose Technology Message-ID: <001c01c11512$da1aab20$2519a8c0@Elroy> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01C114E8.F144A320" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-reply-to: <13EFBBC3DB08D511A5CB0002A5095C5215FA03@mail.workscapeexpress.com> X-OriginalArrivalTime: 25 Jul 2001 13:56:56.0574 (UTC) FILETIME=[AAB599E0:01C11511] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_001D_01C114E8.F144A320 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I haven't really been in on this whole conversation but as a user of the FTP task I think that its biggest shortcoming is the lack of some sort of status while the upload or download is occurring. In most of the scripts where I use the FTP task I am only sending very small files but it still takes 30 - 45 seconds to establish the connection and complete the transfer all the while my build just looks like it's hung.. I know I can use an external FTP program to get around this but doesn't that sort of defeat the purpose of having this capability built into the tool. Any chance we might be able to get a Hash=true option? Just my .02, -=- Kevin -----Original Message----- From: O'Hara, Patrick [mailto:patrick.ohara@workscape.com] Sent: Wednesday, July 25, 2001 8:57 AM To: 'ant-user@jakarta.apache.org' Subject: RE: Trying FTP Again I am disinclined to make FTP work differently from all other tasks. I understand the decision that Ant should end on a failure. I would rather see the retry become part of the task def then part of a particular task, and I don't think that would fly. Patrick O'Hara 262-408-3849 patrick.ohara@workscape.com -----Original Message----- From: Stefan Bodewig [mailto:bodewig@apache.org] Sent: Wednesday, July 25, 2001 12:32 AM To: ant-user@jakarta.apache.org Subject: Re: Trying FTP Again On Tue, 24 Jul 2001, Patrick O'Hara wrote: > classname="org.apache.tools.ant.taskdefs.optional.net.FTP"/> This is redundant. > The idea was to continue to try the FTP task until it works. Hmm, one could add a retry attribute to the task - want to submit a patch? 8-) Maybe it should accept a number (and have a different name) for a maximum of retries, you don't want to have your build running for months just because there is a typo in the build file. Stefan ------=_NextPart_000_001D_01C114E8.F144A320 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE: Trying FTP Again

I haven’t really been in on this whole conversation but as a user of the FTP task = I think that its biggest shortcoming is the lack of some sort of status while = the upload or download is occurring. In most of the scripts where I use the = FTP task I am only sending very small files but it still takes 30 – 45 = seconds to establish the connection and complete the transfer all the while my = build just looks like it’s hung.. I know I can use an external FTP = program to get around this but doesn’t that sort of defeat the purpose of = having this capability built into the tool. Any chance we might be able to get = a Hash=3Dtrue option?

 

Just my .02,

-=3D- Kevin

 

-----Original Message-----
From: O'Hara, Patrick [mailto:patrick.ohara@workscape.com]
Sent: Wednesday, July 25, = 2001 8:57 AM
To: = 'ant-user@jakarta.apache.org'
Subject: RE: Trying FTP = Again

 

I am disinclined to make FTP work differently from all other tasks.  I understand the decision that Ant should end on a failure.  I would = rather see the retry become part of the task def then part of a particular = task, and I don't think that would fly.

Patrick O'Hara
262-408-3849
patrick.ohara@workscape.com



-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]<= /font>
Sent: Wednesday, July = 25, 2001 12:32 AM
To: = ant-user@jakarta.apache.org
Subject: Re: Trying FTP = Again

 

On Tue, 24 Jul 2001, Patrick O'Hara = <patrick.ohara@workscape.com>
wrote: =

>   <taskdef name=3D"ftp"
>       =      classname=3D"org.apache.tools.ant.taskdefs.optional.net.FTP"/&g= t;

This is redundant.

> The idea was to continue to try the FTP task until it works. =

Hmm, one could add a retry attribute to the task - want to submit a =
patch? 8-) Maybe it = should accept a number (and have a different name)
for a maximum of = retries, you don't want to have your build running
for months just because = there is a typo in the build file.

Stefan

------=_NextPart_000_001D_01C114E8.F144A320--