MyEclipse deployed to Tomcat after the project web-inf\classes inside is empty

Today found a strange phenomenon, before the project to run a good, but changed the next string of slogans, the COM2 changed to COM4 after the customer, dead or Alive serial ports do not communicate.

And then in my local use of my tomcat to try is the same problem, changed to COM2 after the normal, before from the appearance.

According to the old routine, 1, the first project clean, and then redeploy, found reported classnofound anomalies,

2, self-check the following project confirmation exists, close the IDE, re-open after the problem is still.

3, restart the computer, because the day before yesterday to the code editing style to change, feel there is a problem, feel beautiful a lot.

4, after the restart is still not, online search said is:

1 "

When the IDE creates the project, the configuration file is generated, and project name is configured in project, and some other IDE-related configurations. There are also some related information in the. mymetadata file, mainly the. classpath file, which is configured with the project Classpath and Jar path, and so on. The last line is
<classpathentry kind= "Output" path= "eis/web-inf/classes"/>
Think you see here should understand what it is to do it. Our project name is EIS, which is where the. class file is generated. You have to check here first. If that's true, clean it. If it doesn't work, you re-create a Web project, copy all the Java code from SRC to the new project, some JSP files on the web, and so on.

2 "

Let's see if you have a little tick off your MyEclipse auto-compilation.
Project----> Bulid automatically before the small tick

3 "
 you are in the Navigator view, see classpath This is the package configuration file.
Inside there is an item
<calsspathentry kind= "con" path= "jdk". Version "/>
Check if the version is correct. Incorrect can be changed manually or through the project right-click--build path--configure Build path to change, Here you can see if each package has no yellow exclamation mark. A yellow exclamation mark identifies that you have not imported a package or a version error, you can choose Remove. In the compilation. Note that the Clssspath file must have a package that does not compile.

, there is no problem checking the items on your own. But see the yellow exclamation point, my project has a red exclamation mark, and then right-click, properties-Inside Java bulid path inside see a library hit Red fork, see below is the corresponding path below I put the jar to delete, and then do not go up after the deployment is good.

The problem is solved, the above is my idea of solving this problem.