问题描述
我已经使用subversion 1.6签出了一堆java代码，然后将这些项目导入eclipse。 Subclipse 1.6拿起了这个事实，除了几个文件夹之外，这个插件是版本控制的。
I have checked out a bunch of java code using subversion 1.6 and then I imported those projects into eclipse. Subclipse 1.6 picked up the fact that the plugins are under version control, except for a few folders.
我现在得到一些错误，如：
I now get a bunch of errors like:
如果我删除项目（从eclipse不在磁盘上）并重新导入，那么修复了一半的时间问题。但是由于我有几十个这样的问题的项目，就意味着把它们重新导入10到20次，然后才能使它们全部工作。这是非常痛苦的，每次有人为svn添加一个新插件，或者由于某种原因需要重新创建一个工作空间时，我都厌倦了。
If I delete the project (from eclipse not on disk) and reimport it, that fixes the problem about half the time. But since I have dozens of projects that are having this problem, it means reimporting them 10-20 times before I get them all working. This is very painful, and I am tired of doing it every time someone adds a new plugin to svn or when I need to recreate a workspace for some reason.
有没有比删除和重新导入更容易解决这个问题？还是有办法首先防止这个问题？
Is there an easier way to fix this than delete and reimport? Or is there a way to prevent this problem in the first place?
推荐答案
这是因为您使用除了Eclipse之外的SVN客户端，然后在Eclipse中导入该项目，并且没有通知Eclipse这是一个SVN项目（即Eclipse不知道它必须忽略SVN元信息）。
This is happening because you checked out a project using an SVN client other than Eclipse and then imported the project in Eclipse and you haven't notified Eclipse that this is an SVN project (that is, Eclipse doesn't know it has to ignore the SVN meta information).
为了正确地解决这个问题，在Eclipse中导入项目之后，Eclipse会意识到项目的SVN性质。
In order to fix this properly, after you have imported the project in Eclipse, have Eclipse be 'aware' of the SVN nature of the project. Do so by
- 选择项目，然后转到团队>分享部分。
- 将出现要求天气这是CVS或SVN项目。选择稍后。
- 它将提示输入凭据，输入它们。
- 完成后，做一个干净的构建。问题消失了
- Select the project and go to the Team > Share section.
- A dialog will appear asking weather this is a CVS or SVN project. Select the later.
- It will prompt for the credentials, enter them.
- When you're done, do a clean build. The problem goes away.
这篇关于为什么eclipse试图将.svn文件夹从src复制到bin，如何使其停止？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！