在导入项目之前，应该将其转换为eclipse项目 MVN eclipse: eclipse 然后我发现以下错误。 在“导入Maven项目”期间发生了内部错误。不支持的IClasspathEntry kind=4

其中是M2E不识别并因此抛出错误的值kind = "var"。

现在输入这个。 MVN eclipse:干净

现在在eclipse中刷新项目或重新导入。

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

or

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

从开普勒升级到卢娜对我来说很管用。

我刚刚为Java 1.8支持添加了一些组件。似乎它们不像我想的那样兼容，或者是我把它们混错了。这真的引起了很多问题。尝试更新系统时报告错误，因为它们无法满足某些依赖项。Maven升级不起作用。我尝试了很多东西。

因此，如果没有理由避免升级，只需将luna存储库添加到可用的软件站点(luna http://download.eclipse.org/releases/luna/)并“检查更新”。最好所有的组件都使用相同的版本，并且有一些不错的新功能。

有时，即使重新导入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 ->更新项目而没有出现错误。

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.