DO NOT REPLY [Bug 16293] New: - using ftp with depends generates error when file is in directory

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16293>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16293

using ftp with depends generates error when file is in directory

           Summary: using ftp with depends generates error when file is in
                    directory
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Optional Tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: mk@fundament.nl
                CC: mk@fundament.nl


Hi,

I am trying to upload some files to an existing directory to ensure that the 
newest versions of the files are uploaded. I am using this command to do so:

<ftp
    server="${ftp.server}"
    userid="${ftp.userid}"
    password="${ftp.password}"
    remotedir="${ftp.remotedir}/${mirror.source.dir}"
    depends="yes"
    verbose="yes">
        <fileset dir="${share-root.dir}">
(...)
        <include name="**\\*xml" />
(...)
    </fileset>
</ftp>

Everything works fine, until a file in a subdirectory has a newer version. The 
ftp task wants to upload this file but is convinced that it should first create 
the directory. And than it fails because the directory already exists! Duh!

See log output:

[ftp] checking date for WEB-INF/communitycfg.xml
[ftp] transferring (...)\WEB-INF\communitycfg.xml
[ftp] creating remote directory WEB-INF
[ftp] disconnecting

BUILD FAILED
file:(...)/build.xml:98: could not create directory: 550 Failed to create 
directory."(...)/WEB-INF"

Note: I left out some really long paths (...) because they are irrelevant here.

Did I do something wrong here? Or has someone encoutered this problem before 
and has thought of a solution or workaround?

thanks,
Marten

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>