你的问题听起来好像你试图解决一些我们还不知道的问题。所以我在这里略作猜测,如果问题表明我错了,我会改变答案。

• (Part of your) development has to live on the server, so there are resources you have to use during development, which are necessary for development.
• Possibly these resources are (only) necessary for testing (unit tests?), or for functional tests.
• You have experience with Eclipse and want to use that.

下面是可能对你有用的可能解决办法的草图。

Using Eclipse on the server

• You install an appropriate eclipse distro on the linux machine you have to develop on.
• You install locally e.g. Cygwin with the XWin packages that allow you to start an X-windows server locally.
• You open up an xterm locally (just to get the display variable correct).
• You start from that xterm the eclipse installed on the Linux machine: ssh <user-id>@<ip-of-linux-server> <path to eclipse> -display $DISPLAY

Pros and cons

• + You work on the machine and have the display locally.
• + You are able to checkout directly on the machine, no need of a local copy.
• - Your are not able to work without the connection to the Linux machine.

Using Eclipse locally

有两个变式,两者都有价值:

• Have the sources on the server (only)
• Have the sources locally

Sources on server, Eclipse locally

最简单的方式是挂载服务器的文件系统, 这样您就可以通过不同的驱动器来访问本地 。 询问您的系统管理员如何完成 。

Pros and cons

• + Everything works as normal.
• + You don t have to install Subversion on the server.
• - Latency for the remote file system may be annoying.
• - You are only able to work with network connection to the server.

Sources locally, Eclipse locally

这是正常的操作方式。 按常态安装 Subversion 插件的剪贴板插件, 从仓库取出, 本地工作( 甚至断开), 执行您的更改 。

然后,您可以通过在服务器上进行检查测试,在那里建立系统,在那里进行单位测试和集成测试。

Pros and cons

• + Easier to install and maintain.
• - No tests during development without a build process in between.
• - Tests can only be done with commited code, not with changes that are not commited.

My recommendation

我喜欢在服务器上使用剪贴板的解决方案, 所以您可以使用服务器上的所有可用设备, Linux 下的剪贴板和 Windows 下完全一样。 您在测试之间没有任何步骤, 一切都在本地完成( 在服务器上 ) 。

另见下列问题(和答案):

• Is it possible to work on remote files in Eclipse?

PS:我忘记了:我认为 svn+ssh 只是不同的 Subversion 协议来进行校验、更新和承诺。 使用协议( file:// , svn:// , /code > 或甚至 https:// )。