The attached patch adds the ability to specify a
private key for authentication while using svnAnt and
the svn+ssh protocol. It basically addresses the same
issue that was discussed back in August, but I didn't
see a patch for that one
(http://subclipse.tigris.org/servlets/ReadMsg?list=dev&msgNo=2584).
An example of my build.xml is:
<svn passPhrase="superSecret"
keyFile="C:\id_dsa"
trustInvalidSslServer="AcceptPermanently"
sshPort="22">
<info target="${infile}" />
</svn>
This was put together quickly, and its current
stability level is "It seemed to work for me" (TM). If
you want to apply the patch, I would suggest further
testing.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Fri Dec 28 20:27:01 2007