“SVN存储库”当您切换工作区时总是出现空白是否有插件可以让Eclipse记住它们？ [英] "SVN Repositories" always comes up blank when you switch workspaces Is there a plugin to get Eclipse to remember them?

问题描述

例如，假设您在一个工作区中从SVN存储库中签出了一个项目，但它包含多个项目（相关或不相关）。您切换到新的工作区，并执行

Window | Perspective | SVN存储库探索。

Eclipse现在已经忘记刚才使用的存储库。你看到一个空白列表。而且你必须重新关闭存储库链接。

是否有一个插件可以帮助Eclipse记住工作空间之间的仓库列表？ （IntelliJ Idea，例如，自动执行）？

谢谢！

编辑：我没有意图破坏工作区的分离性或完整性。其实这就是整体。你不行使用多个存储库工件侵入一个工作区是令人难以置信的混乱。

只有一个工作区也不实用。当工作区正在使用中时，计算机会崩溃。人们使用不同的IDE。人们检查造成构建事故的材料。工作区休息。

我们有开发人员必须使用多个存储库。想要访问多个存储库的方便。当你只有一个时，Eclipse是好的。

但是，在多项目工作环境中也需要实用，项目中其他组织的其他开发人员甚至不使用Eclipse。而在Eclipse中，只有一个工作空间（这显然是原始的意图）似乎不实用。要使一个工作区跟踪您要使用的所有存储库？我不能说

但是，我意识到Eclipse的原始意图可能不是为了跟踪您的存储库。但是，尝试回想一下，当电脑被创造时，他们只用于遥测数据，打破代码，并做出冯·诺伊曼（John Von Neumann）难以置信的富有想象力的想法。

最初创建Eclipse的人无法想像最终将被用于管理OSGi服务器。或许多语言：Haskell，Scala Python或Ruby。

或Maven。或者显然，单个开发人员可能同时处理多个项目，并且可能需要多个工作空间来成功管理一个项目。但是我们这样做。没有人创造一个IDE可能会想到所有可能的最终用途，或者将来会面临许多年的问题。

因此，创建了插件。我只是问是否有一个插件可以保持Eclipse在这方面的竞争力。我不是想打败IDE的整个意图，我认为这样做会使生活更轻松。现在，我觉得你告诉我，不记得存储库是传统，我就像Tevya问

它会破坏一些广阔的永恒计划，
如果我们有一个持久的SCM存储库列表？

但生活依然存在，一个项目有自己的工作流程和构建流程，开发人员必须跟上。我们的工具是Eclipse。

如果Eclipse可以以某种方式保留我使用的列表或存储库，那么这样做会很好，以一致的方式使用Eclipse IDE，而不需要另一个程序来管理这个。

如果你读了这么远，谢谢阅读。

解决方案

不，因为这样做是为了工作。工作区完全分开。如果我有一个工作区，例如PHP项目为什么我应该使用指向Java项目的存储库位置来污染其存储库浏览器？

如果要保留设置，您基本上有两种方式：创建一个新的工作区，但复制旧的工作区文件夹，重命名并删除不需要的项目（从Eclipse中删除！）。

或者您导出/导入特定的设置。为此：菜单文件>导出... /导入... 一般>首。然后，您可以选择要导出的元素，包括SVN存储库位置。

当然在两个工作区之间没有实时更新。正如我所说，因为它是打算这样工作。

For example, say you have a project checked out from SVN Repository in one workspace, but it contains several projects (either related or not). You switch to a new workspace and do

Window |Perspective | SVN Repository Exploring.

Eclipse has now "forgotten" the repository you were just using. You see a blanks list. And you have to go key in the repository link all over again.

Is there a plugin that will help Eclipse remember a list of repositories between workspaces? (IntelliJ Idea, for instance, does this automatically)?

Thanks!

Edit: I had no intention of destroying the separateness or integrity of a workspace. In fact, that's the whole point. You can't. Invading one workspace with multiple repository artifacts is incredibly confusing.

Nor is it practical to only have "one" workspace. Computers crash while the workspace is in use. People use different IDEs. People check in material that makes a build crash. Workspaces break.

And we have developers who have to use multiple repositories. would like the convenience of having access to multiple repositories. Eclipse is fine when you only have one.

But it also needs to be practical in a multi-project work environment, where other developers in other organizations on a project do not even use Eclipse. And it has not seemed practical in Eclipse to only have one workspace (which clearly was the original "intent"). To make one workspace track all the repositories you're going to use? I can't say.

However, I realize the original intent of Eclipse might not have been to track your repositories for you. But try and recall, when computers were created they were only used to operate on telemetry data, to break codes and to do the things that John Von Neumann's incredibly rich imagination could think up.

The people who originally created Eclipse could not envision that it would be eventually be used to manage for OSGi servers. Or many language: Haskell, Scala Python or Ruby.

Or Maven. Or apparently that a single developer might work on more than one project at the same time and might ever need more than one workspace to successfully manage one project. But we do. No one creating an IDE could possibly think of all the eventual uses that it might be put to, or problems it would face many years into the future.

Thus plugins are created. I was just asking whether there is a plugin that keeps Eclipse competitive in this area. I'm not trying to defeat the whole intent of the IDE, which I would think is to make life easier. Now, I feel like you're telling me that NOT remembering repositories is "tradition" and I'm like Tevya asking

"Would it spoil some vast eternal plan, if we had a persistent SCM repository list?"

But life goes on, a project has its own workflow and build flow and developers have to keep up. The tool we have is Eclipse.

And to keep up it would be nice if Eclipse could somehow retain a list or repositories that I use, and it would be nice to do this in in a coherent way using the Eclipse IDE, and not requiring yet another program to manage this.

If you read this far, thanks for reading.

解决方案

No, because it is intended to work this way. Workspaces are completely separate. If I have a workspace for e.g. PHP projects why should I pollute its repository browser with repository locations that point to Java projects?

If you want to keep settings you have basically two ways: Either you don't create a new workspace but copy the old workspace folder, rename it and delete unneeded projects (delete from within Eclipse!). This way all your settings (like fonts, perspectives) are preserved.

Or you export / import specific settings. For this: Menu File > Export... / Import... General > Preferences. Then you can select the elements you want to export, including SVN repository locations.

Certainly there is no "live" update between two workspaces. As I said because it is intended to work this way.

这篇关于“SVN存储库”当您切换工作区时总是出现空白是否有插件可以让Eclipse记住它们？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！