Since Eclipse has never replaced the IDE, although also tried NetBeans, idea, etc., but the total feeling is not easy to use, shortcut keys can not find, and finally returned to eclipse. However, Eclipse occasionally played a small temper, there are some inexplicable problems. The following three are often encountered during this period of time.
1. ClassNotFoundException is prompted when run on server in Eclipse.
There is no sign of this problem, the normal operation of the program, but suddenly can not start. In the console, you see Java.lang.ClassNotFoundException, and the classes that you can't find each time are different, sometimes the classes I create myself, sometimes the third-party packages I introduce. But those things are clearly there, there is no compilation errors, but the server is not up.
Workaround: in the Java EE perspective, locate the server view (which can also be opened in other perspectives), right-click on the server that you want to run (such as Tomcat v7.0 Server at localhost), and then select Clean. This method can at least ensure that the next boot is normal, and when the ventilation.
2,Eclipse official Maven plugin does not recognize WTP Project.
Using MAVEN to manage your project's build and dependencies is a lot easier, you don't need to install a bunch of plug-ins, and you don't need to worry about the management and update of dependent libraries. When the M2eclipse plug-in was first used, the plugin's official website was still on the Sonatype, http://m2eclipse.sonatype.org/, and the installation was two plugins core and extras (http:// m2eclipse.sonatype.org/installing-m2eclipse.html). But then one day, once again came to http://m2eclipse.sonatype.org/, found that the plugin has been migrated to the Eclipse website notice. At that time thought, this is good, certainly the combination of the two will be more closely, to our developers should be a good thing. However, after the new Guide (http://eclipse.org/m2e/download/) was installed, it was discovered that the official Eclipse plug-in, which did not support WTP, was unable to identify the original project in a dynamic Web project. It's disappointing:-(
workaround : project→ The right mouse button "Properties" → select "Project Facets" from the list on the left to check the "Dynamic Web Project" on the right, and pay attention to selecting the correct version.
3., and 2 are related issues, you cannot choose Dynamic Web project from project Facets.
In general, when you encounter an unrecognized dynamic Web project, you can resolve it by using the 2 method. But a colleague came across another situation yesterday: After using existing Maven projects to import a project, only the Src/main/java is identified as the source folder for project. Both test and resources are treated as normal directories (when you create a new MAVEN project, you are creating only the Src/main/java and Src/main/webapp folders, none of the others are created). He added Src/main/resources, Src/test/java, and src/test/resources to source Folder, and when he was debugging in eclipse, he found out that it was not a web Project, Unable to run on Server. Then follow the steps in 2 to add the facet of dynamic Web project, always prompting for errors.
Workaround: first remove the folders except Src/main/java from source folder, add them as dynamic Web Project, and finally put the other folders back into source folder.
Although eclipse is sometimes unstable, it will run very well, but overall it is still good. I hope it gets better.