Hello Paul,
I received similar bug report today, and I agree there is probably a bug in
JavaSVN that causes that problem. I expect it to be fixed in the next
version of the library that will be published next week.
From the first glance it doesn't look like port number is not saved
correctly, so this problem needs more investigations. Thank you for your
suggestion, in case I will need more information I will contact you.
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Paul Lechnar [mailto:paul@mis.com]
> Sent: Wednesday, February 15, 2006 8:45 PM
> To: users@subclipse.tigris.org
> Subject: [Subclipse-users] caching of SSH connection
> properties does not store nonstandard SSH Port
>
> I have confirmed this problem using Subclipse 0.9.106 and
> Eclipse 3.2M4, running on Windows XP (same problem on two
> separate machines)
>
> When using JavaSVN (Pure Java) to connect to a subversion
> repository, I have observed the following behavior:
>
> When first setting up a repository, using the svn+ssh://
> protocol, the SSH connection properties dialog appears,
> allowing for entry of a username,password and SSH port (also
> a public key, but I'm not using that in this example).
> After filling out the appropriate info, *including* a
> non-standard SSH port (e.g. 3222) and checking the "save
> info" checkbox, the connection commences and is successful.
> Furthermore, any subsequent connections within that eclipse
> session work fine (commits, syncro, updates ,etc)
>
> However, once Eclipse is shut down and then restarted, any
> SSH connections will time out, and I have confirmed with a
> TCP monitor program that Eclipse is attempting to connect to
> the subversion host on port 22, the standard SSH port.
> Deleting the keyring file at
> {ECLIPSE_DIR}\configuration\org.eclipse.core.runtime\.keyring
> will cause the SSH connection properties dialog to re-appear
> the next time I try to connect to the repository, and again,
> properly filling out the form will allow Subclipse to work
> fine for that Eclipse session.
>
> This leads me to believe that when storing the connection
> properties for that host (perhaps in the keyring file?), the
> SSH port number is not being saved correctly.
>
> If anyone has any ideas, or if the developers need more info
> for a bug report, please feel free to contact me.
>
> Regards,
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Feb 15 18:57:46 2006