MyEclipse The Export War package issue

The two days are busy with a project on the line, and now summarize the solution of a strange problem encountered.

The company uses a Windows system server, so it saves a lot of Linux cumbersome commands. Deployment work is a lot simpler. All ready to end, put on the war package starts the server, but does not have access to the project, the repeated deployment still does not solve the problem, the project has been decompressed. It is strange, in the normal use of the machine, after packaging but not, suspicion is the issue of war, and then I put the project of the machine is not packaged, put on the server to start, oh, normal.

In order to find the cause of the problem, I compared the pre-packaged project with the extracted project of the war package using the Compare tool, and found that all the jar packages and configuration files related to the log were lost. This is why it is not possible to access the server without prompting for any reason. Then on the internet to find a lot of questions about MyEclipse packaging, although there are similar problems but lost content is different, the solution is not the same. Some also found the cause of Tomcat, I do not apply to this problem. So I tried another way of packaging, that is to find the MyEclipse configuration of the development of Tomcat in servers, deploy the project when the war package to deploy the form, and click Finish. This allows you to have a war package on top of your server and then deploy it on a remote server with this war package. The haha problem is solved.

This is the only record, hoping to help some detours of friends.

MyEclipse The Export War package issue