我在STS中导入了maven项目,当我运行更新更新项目时,我收到:

"Updating Maven Project". Unsupported IClasspathEntry kind=4

有什么解决办法吗?


当前回答

确保您正在运行的m2e(clipse)插件的版本至少为1.1.0 关闭maven项目-右键单击“关闭项目” 手动删除。classpath文件中所有带有kind="var"的classpathentry 开放项目

or

删除maven项目 手动清除.classpath 4再导入项目

其他回答

I tried Marco's steps but no luck. Instead if you just get the latest m2e plugin from the link he provides and one by one right click on each project -> Maven -> Update Dependencies the error still pops up but the issue is resolved. That is to say the warnings disappear in the Markers view. I encountered this issue after importing some projects into SpringSource Tool Suite (STS). When I returned to my Eclipse Juno installation the warnings were displaying. Seeing that I had m2e 1.1 already installed I tried Marco's steps to no avail. Getting the latest version fixed it however.

我尝试了这里提到的所有步骤和类似的问题,但不能解决这个问题。我既不能解决问题,也不能更新我的m2eclipse。所以我安装了Eclipse Luna,它解决了我的问题……尽管这意味着我必须花45分钟来配置我的工作空间中的所有环境。

如果更新命令用于用于Clover代码覆盖的项目,也会抛出此错误。

在此情况下解决: 取消要更新的项目文件夹。 再次运行maven更新,然后使用工具进行代码覆盖。

有时,即使重新导入Maven项目也无法工作。在eclipse中正确地更新项目并不是一个确定的过程。 我发现的唯一100%安全的程序是:

Disable Maven Nature, run mvn eclipse:clean, restart, cross your fingers and Pray 3 times. If this won't work, delete the project, run mvn eclipse:clean, re-import refresh, pray and use the force. If this still doesn't work, restart Eclipse, or even better your computer. While waiting for the reboot, you can make a random donation to fix your Karma. Repeat step 2 and don't forget to pray and control your anger. Anger leads to hate. Hate leads to suffering. Try all the other answers posted in this thread. You might need to try them all for 3 times at least before giving up. Format your Computer, re-install Eclipse and Maven. No need to pray anymore, all gods hate you anyway Delete your git project, burn the physical drive that stored the remote repository, and write your project from scratch. Find a time machine, travel to the past and convince yourself to follow another, non-programming career or at least to avoid Java

看到所有其他答案。我找到了一个更简单的方法。

我只是删除了.classpath(用eclipse编辑)中包含var的所有行,并使用maven ->更新项目而没有出现错误。