It probably has more to do with the authentication method on the server. Our developers recently were experiencing problems with cvs within eclipse, where the ext method worked fine(system command ssh) but not with extssh(eclipse builtin) after our sysadmin changed over to LDAP authentication. The problems were similiar to what you describe. Our system admin turned on nscd(name service cacher) and in the /etc/ssh/sshd_config file on the server, uncommented the line that said "Protocol 2,1" since the default for ssh is protocol 2 but Eclipse uses protocol 1. Assuming that Eclipse uses some basic Java ssh/scp api and Maven does the same, the problem may be the same.
Hope this helps. Eric On Fri, 2005-04-22 at 10:19 -0400, Maven Users List wrote: > I have a bit of a problem understanding why these 2 (scp and scpexe) > behave so differently. I know the scpexe actually calls the command > while the other runs from java, but with my setup (Fedora Core 3, jdk > 1.5, maven 1.0.2), the scpexe takes a very long time to complete, but > works every single time. While the scp executes much faster but gives > me > sporadic SSH_MSG_DISCONNECT errors, sporadic in the sense that it > never > occurs at the same place, but still consistent enough to break any > build > that implies 2-3 artifact deployment. > > > Are those known issues? I can keep things working using scpexe, but > I'd > really prefer getting the speed of scp... Any suggestions? > > > Thanks, > Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
