On 10/8/05, Ashley Williams <[EMAIL PROTECTED]> wrote: > Tricky to try out sftp, but will do so as soon as my build stops > failing - > artifact downloads are currently being truncated to 64k from my apache > server.
note that sftp:// is the ssh2 version, not the other one (it's confusing). So it should work with a normal sshd. Another option is scpexe which forks your scp executable from the path (this requires an extensions element with o.a.m.wagon:wagon-ssh-external). > Interesting info about the scp -t option since my client and server are > on the same machine (only have the one), but this hasn't made a > difference before. In fact I've just checked and I can scp files ok by > hand, although I don't use that -t option. Yes, it isn't aware of that, it still opens a channel on localhost:22 and then execs scp -t to copy the file onto the open channel. Of course, if you are on localhost, why not use file:// ? > Not been a terribly successful foray into setting up a repository so > far... > > (can only get better) Hope so! - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
