eclipse Subclipse 中的 JavaHL 错误

JavaHL Error in Subclipse

提问by Nalum

I'm trying to create a new phonegap project in a new repository. When ever I add a new folder or file I get the following error. This is a completely fresh copy of eclipse in a new workspace and fresh install of subclipse.

我正在尝试在新存储库中创建一个新的 phonegap 项目。每当我添加新文件夹或文件时，都会出现以下错误。这是在新工作区和全新安装的 subclipse 中的 eclipse 的全新副本。

Errors occurred while updating the change sets for SVNStatusSubscriber

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' is not a working copy

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' is not a working copy

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' is not a working copy

更新 SVNStatusSubscriber 的更改集时发生错误

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' 不是工作副本

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' 不是工作副本

org.apache.subversion.javahl.ClientException: svn: E155007: 'Workspace/PhoneGap/www/js' 不是工作副本

I've no idea what is causing the issue, everything I've found through google has said a fresh install or fresh workspace should fix the issue. I've also selected SVNKit to be the SVN Client as I've had issues with JavaHL before and the fix was to switch to SVNKit.

我不知道是什么导致了这个问题，我通过谷歌找到的一切都说全新安装或全新的工作区应该解决这个问题。我还选择了 SVNKit 作为 SVN 客户端，因为我之前遇到过 JavaHL 问题，解决方法是切换到 SVNKit。

Eclipse Installation and Versions:

Eclipse 安装和版本：

采纳答案by Mark Phippard

For whatever reason, it looks like the SVNKit 1.7.x API (which is still in beta) does not think that folder is a working copy. I cannot really say if it is right/wrong or why, but that is the error the API is throwing.

无论出于何种原因，看起来 SVNKit 1.7.x API（仍处于测试阶段）不认为该文件夹是工作副本。我真的不能说它是对还是错或为什么，但这是 API 抛出的错误。

They have released a beta2 recently. You could get that update from their update site.

他们最近发布了一个 beta2。您可以从他们的更新站点获取该更新。

If you have SVN 1.7.x command line you could use it to examine the WC and that folder using the svn status command.

如果您有 SVN 1.7.x 命令行，您可以使用它来检查 WC 和使用 svn status 命令的文件夹。

回答by rawb

I have the same issue, but get the error in my /binfolder. Obviously my /binfolder is not svn-added to my remote svn server... because we don't want to keep binaries in addition to source in svn.

我有同样的问题，但在我的/bin文件夹中出现错误。显然我的/bin文件夹没有通过 svn 添加到我的远程 svn 服务器......因为我们不想在 svn 中保留二进制文件和源文件。

After trying to clean-build my projects, I got the same error. I assumed the svn plugin was somehow mucking stuff up, and disabled them. (in osgi console, stop all the id's related to svn).

在尝试清理构建我的项目后，我遇到了同样的错误。我认为 svn 插件不知何故搞砸了，并禁用了它们。（在 osgi 控制台中，停止所有与 svn 相关的 id）。

I then got hte following stack trace:

然后我得到了以下堆栈跟踪：

java.lang.NullPointerException
at org.tigris.subversion.subclipse.core.SVNClientManager.getAdapter(SVNClientManager.java:127)
at org.tigris.subversion.subclipse.core.SVNClientManager.getSVNClient(SVNClientManager.java:94)
at org.tigris.subversion.subclipse.core.SVNProviderPlugin.getSVNClient(SVNProviderPlugin.java:462)
at org.tigris.subversion.subclipse.core.repo.SVNRepositoryLocation.getSVNClient(SVNRepositoryLocation.java:274)
at org.tigris.subversion.subclipse.core.resources.SVNMoveDeleteHook.deleteResource(SVNMoveDeleteHook.java:47)
at org.tigris.subversion.subclipse.core.resources.SVNMoveDeleteHook.deleteFolder(SVNMoveDeleteHook.java:110)
at org.eclipse.team.internal.core.MoveDeleteManager.deleteFolder(MoveDeleteManager.java:62)
at org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1940)
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:780)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.cleanOutputFolders(BatchImageBuilder.java:114)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:46)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
at org.eclipse.core.internal.events.BuildManager.run(BuildManager.java:728)

Now this stack trace is due to me stopping the plugins, but, it does give a clue what was happening beforeI disabled the plugins.

现在这个堆栈跟踪是由于我停止了插件，但是，它确实提供了在我禁用插件之前发生了什么的线索。

It seems that svnkit is now treating the deletion of my bin folder (which gets deleted as part of a clean build process) as an error, since my bin folder has no .svn subfolder (aka is not a working copy).

似乎 svnkit 现在将删除我的 bin 文件夹（作为干净构建过程的一部分被删除）视为错误，因为我的 bin 文件夹没有 .svn 子文件夹（也就是不是工作副本）。

So this means their code somehow assumes that all folders shouldbe a working copy, and if they're not it's an error. Their code seems to ignore hte possibility that I might have a folder in my local tree that I do notwant to commit remotely.

所以这意味着他们的代码以某种方式假设所有文件夹都应该是一个工作副本，如果不是，那就是一个错误。他们的代码似乎忽略兴田可能性，我可能有一个文件夹在我的本地的树，我不希望远程提交。

balls.

球。

回答by sandhya

I had the same annoying problem with bin complaining. I checked in workspace/preferences/Team/svn

我遇到了与 bin 抱怨相同的烦人问题。我检查了工作区/首选项/团队/svn

There in client, I had option of SVNKit or JavaHL. I changed mine from javahl to SVNkit and restarted. The problem seems to have gone :-)

在客户端，我可以选择 SVNKit 或 JavaHL。我将我的从 javahl 更改为 SVNkit 并重新启动。问题似乎已经解决了:-)

I also deleted the bin folders for the complaining projects and did the above. Maybe combination should work for other cases. I presume it was the JavaHL that was the problem.

我还删除了抱怨项目的 bin 文件夹并执行了上述操作。也许组合应该适用于其他情况。我认为问题出在 JavaHL 上。

回答by Christoph

I also got this error after upgrading my Eclipse.

升级我的 Eclipse 后，我也遇到了这个错误。

svn: E155007 '/somepath' is not a working copy

The reason was that I was still running SVN 1.6 on my MacOSX machine (run svn --version on command line) but downloaded Subclipse 1.10 which seems to require SVN 1.8

原因是我仍然在我的 MacOSX 机器上运行 SVN 1.6（在命令行上运行 svn --version）但下载了 Subclipse 1.10，它似乎需要 SVN 1.8

I had to install Subclipse 1.6 in order to remove this strange message.

我必须安装 Subclipse 1.6 才能删除这个奇怪的消息。

Side note: After re-installing subclipse, I also had to remove all bundles in the project and import them again, so that the SVN folders got recognized

旁注：重新安装 subclipse 后，我还必须删除项目中的所有包并再次导入它们，以便识别 SVN 文件夹