RE: [Subclipse-users] SSH port number not saved; reverts to default value in 1.0.4 (works in 1.0.3)

After you removed the 1.0.4 jars did you have to check out the
repository again? A co-worker of mine is having this problem. We
removed all the 1.0.4 jars and he still had the 1.0.3 files. Now he
lost all connection with the repository and it appears we have to
checkout again.

Thanks,
Tom

-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Thursday, December 14, 2006 7:40 AM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] SSH port number not saved; reverts to
default value in 1.0.4 (works in 1.0.3)

On 12/14/06, Greg Kopff <gkopff@powersource.com.au> wrote:

I just upgraded my version of Eclipse to 3.2 (on Linux) and downloaded
the latest version of Subclipse (1.0.4).

Since you are on 3.2, you should install the 1.1.9 version.
 

We use svn+ssh, but run ssh on a non-standard port (ie not 22).

When I first checkout my project, Subclipse prompts me for my
credentials: username, password and port number (I use password
authentication rather than key based).

I then click the checkbox to tell Subclipse to save this information.

I then close Eclipse, and then re-open the application. If I then try
to synchronise with the repository, I get an error dialog back, and the
SVN console reports:

   svn: Cannot connect to 'svn+ssh://server/': There was a problem while
connecting to server:22

I believe someone else reported this last week. It appears to be a
problem in SVNKit. 1.1.9 would have the same problem as it is using the
same version of SVNKit. I will email the developers of SVNKit since
they do not seem to be reading this list anymore.

Mark

 
Received on Tue Dec 19 15:46:59 2006