Eclipse startup project FAQ

I encountered a problem today. When eclipse takes tomcat to run a project with development tasks, it keeps prompting that some classes cannot be found. In fact, these classes exist, and then various problems are found. After checking the configuration of tomcat in eeclipse, I found something:


the configuration here probably means that eclipse's personalized configurations for various projects in the current workspace are placed here, including what configurations are currently loaded in tomcat in eclipse, etc. The information is all configured here.
The explanation for this configuration is probably found online:
https://www.baidu.com/s?wd=%E5%B7%A5%E4%BD%9C%E7%9B%AE%E5%BD%95% E4%B8%8B%E7%9A%84.metadata%E6%98%AF%E5%B9%B2%E5%98%9B%E7%9A%84&rsv_spt=1&rsv_iqid=0xf42c7a5300004ef6&issp=1&f=8&rsv_bp=1&rsv_idx=2&ie= utf-8 & rqlang = cn & tn = baiduhome_pg & rsv_enter = 1 & oq = tomcat% 2520server% 2520locations% 25E6% 2598% 25AF% 25E5% 25B9% 25B2% 25E5% 2598% 259B% 25E7% 259A% 2584 & rsv_t = 8f68psXLNTfrOdeetGaSXaQEFDiOHX5a9kzLkUmlRZ9cmBvIxrJuwvopO4bMK2suokTj & inputT = 6549 & rsv_pq = f742e5db00001011 & rsv_sug3 = 123 & rsv_sug1 = 71 & rsv_sug7 = 100&rsv_n=2&rsv_sug2=0&rsv_sug4=7393
https:

The reason for the problem is:
when adding or removing (add and remove) projects to tomcat in eclipse, the related project files in the directory workspace\.metadata\.plugins\org.eclipse.wst.server.core The configuration has not been added or removed cleanly, causing it to fail . The solution at this time is to clean up the project folder that has not been deleted in this directory (you can find the file or folder according to the project name). A more thorough solution is to delete all the files and folders in this directory, then re-import the project in eclipse, and reconfigure tomcat to start.

This is a frequently encountered problem, and I often try to solve it, and it works!


In addition, the common problems that the tomcat startup project cannot start up. Common debugging operations are:
1. Right-click on the project and tick Maven update (tick Force Update of Snapshots/Release);
2. Clean up useless items in Deployment Assembly;
3. In Project Facets Modify the java version used;
4. Delete the packages under com/qlk in the local warehouse, and re-maven update the packages on the private server;
5. The workspace\.metadata\.plugins\org.eclipse in the local working directory. All the things below wst.server.core\temp0 are cleaned up;
6. Right-click on tomcat to publish to publish;
7. Manually clean up tomcat:
https://jingyan.baidu.com/article/b24f6c82e76af886bfe5dad3.html
8. Frequently clean up the following of temp0: everything under
work\Catalina\localhost
Everything under wtpwebapps


eclipse needs to do to switch the new workspace:
1. Modify the encoding method of the new workspace
2. Add tomcat
3. Modify tomcat startup timeout

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326646273&siteId=291194637