Alexis Gallagher <firstname.lastname@example.org> wrote on 03/11/2005 06:50:53
> I'm having problems using the svn+shh:// protocol in subclipse on OS X
> (Eclipse 3.01 and subclipse 0.9.28).
> If I use svn from the command line, or if I use subclipse on my WinXP
> box, then I can connect to my repository via svn+ssh://. But from
> subclipse on my OS X machine, trying to use svn+ssh:// generates an
> error. All of this is despite the fact that svn:// and http:// work
> Maybe my problem is due to a conflict between Metissian's subversion
> code and fink's subversion code. Originally, I used fink to setup both
> my subversion server and client code on my machine. But after
> subclipse crashed with this, I uninstalled fink's svn client code and
> installed the Metissian package. I thought that Metissian package was
> client code (correct?), so I left the fink server package and
> repository in place. Maybe they are bumping into each other?
> I am sure the problem must be with subclipse, and not the server
> package, because I am able to connect to my server using svn+ssh://
> from subclipse on my Windows machine.
> If anyone has advice on whether fink and Metissian play well together,
> or if I can do away with one of them, I'd be much obliged.
If the svn command line works, then in theory Subclipse ought to work.
Subclipse does not really have any code that is specific to your access
method. We are just passing the URL through to the JavaHL layer and all
of the work happens in JavaHL and the Subversion libraries. I believe for
svn+ssh:// it would rely a lot on the Subversion configuration area for
knowing what to do. One thing you could try is playing with that SVN
Preference in Eclipse that allows you to point to a specific configuration
Another option would be to try JavaSVN since it has an entirely different
way of handling the ssh part.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Mar 12 00:19:34 2005