Dear Sorin, Thanks for this clarification. So I will see what the SCPlugin developers think about this issue. All the best, Christian Sorin Ristache wrote:
Hello,
Do you mean that you tried to load the working copy created with the Oxygen SVN client in other SVN client tool and that failed? It should not fail as including the server port in a URL is a perfectly valid way of telling the clients where the server can be contacted. I think the behavior of the Oxygen SVN client is correct: it creates a SVN working copy with administrative files containing a valid URL.
The message 'Connection error' is too general. Are there more details about the cause of the error, maybe a stack trace in a log file?
Regards, Sorin
Christian Wittern wrote:
Hi there,
Recently, I ran into some issues with the SVN client, so I thought I talk about them here to see if there is a way to resolve the problem.
I am using the svn+ssh protocol to tunnel the svn connection through ssh For security reasons, my ssh server has an unusual port.
Now oxygen seems not to look at the configuration for SSH in ~/.ssh/config which means I have to specify the port on the URL like: svn+ssh:/<server>:<port>/path/to/rep This allows me to access the repository from within Oxygen. The problem with this is, however, that it makes other SVN tools fail. So if I want to use SCPlugin (this is the Mac equivalent to TortoiseSVN), it fails with a 'Connection error'.
While I do not know which of the two behaviors is correct, I think it could be solved if Oxygen would allows to specify the port separately from the repository URL. But there might be other solutions as well?
Any hint appreciated,
Christian
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN