Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 97987 invoked from network); 6 Mar 2003 18:11:28 -0000 Received: from medusa.stargus.com (HELO xchange.stargus.com) (65.193.169.162) by daedalus.apache.org with SMTP; 6 Mar 2003 18:11:28 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Change to FTP behavior in ant 1.5.2? Date: Thu, 6 Mar 2003 13:11:28 -0500 Message-ID: <9093431B64301C47986EF078512912AD7B8221@xchange.stargus.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Change to FTP behavior in ant 1.5.2? Thread-Index: AcLkCqXzKIFhr90DSmq5s+tRSRL7twAAPu6g From: "Matt Lyon" To: "Ant Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Steve, Thanks for the heads up on this. I've filed the new bug, #17735 in = Bugzilla. FYI, I did already have ignorenoncriticalerrors set to true in = my task. Matt -----Original Message----- From: Steve Loughran [mailto:steve_l@iseran.com] Sent: Thursday, March 06, 2003 1:02 PM To: Ant Users List Subject: Re: Change to FTP behavior in ant 1.5.2? file a bug. there were changes in the task that were intended to work = round problems where creating dirs which already existed raised errors in the process -now we try and CD to the dir, if we cant it should be created. Something bad is happening here. state your server type in the bugrep. Also, try setting ignorenoncriticalerrors=3D"true" in . ----- Original Message ----- From: "Matt Lyon" To: "Ant-User (E-mail)" Sent: Thursday, March 06, 2003 08:52 Subject: Change to FTP behavior in ant 1.5.2? Hi, I've noticed that upgrading to 1.5.2 seems to have "broken" one of my = ftp tasks. The ftp task in question uploads a several levels deep directory structure to a remote system. This always worked fine in the past, but = in Ant 1.5.2, I get the following: BUILD FAILED file:C:/master/starman/build/build.xml:1588: could not change to = directory: 550 starnode\admin: No such file or directory. The issue is caused by the fact that I don't explicitly create all the directories on the remote system, only the top level directory, and in = the past, Ant seemed to just generate the remote sub-directories under the = top level directory as needed during the transfer on the fly. Is this = something to do with separators ('/' Vs. '\') being changed in Ant 1.5.2? It looks like the fact that it's coming from Window$ and going to Unix and the separators is the issue, but this was never a problem in the past... Matt --------------------------------------------------------------------- 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