有时，即使重新导入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

试一试 mvn clean install eclipse:在DOS命令提示符上执行eclipse -Dwtpversion=2.0命令。 暗示你是因为，这招对我很管用!!

你有没有试过:

如果您有导入项目到eclipse 4，请删除它。 在maven consol中，运行:mvn eclipse:clean Eclipse 4: File -> Import -> Maven ->现有Maven项目

我使用Eclipse 4.3.2 (Kepler)和M2E 1.4。X和摸索了好几次这个问题!

在我的情况下，“mvn eclipse:eclipse”命令还生成Checkstyle, PMD和Findbugs配置，所以“mvn eclipse:clean”对我没有帮助，因为它会再次删除所有这些配置文件。

对我来说，最好的解决办法就是删除所有。”类路径”文件:

find . -name ".classpath" -delete

然后将项目导入eclipse。

有时，即使重新导入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

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.