D? E? P? L? O? Y? M? E? N? T? ? F? A? I? L? U? R? E? ? O? N? ? T? O? M? C? A? T? ? 6 ?.? X ?.? ? C? O? U? L? D? ? N? O? T? ? C? O? P? Y? ? A? L? L? ? R? E? S? O? U? R? C? E? S? ? T? O

There has been a problem in the overall myeclipse deployment project, and the following error is prompted. After studying the online demand help, the solution is as follows:

Deployment failure on Tomcat 6. x. cocould not copy all resources to D:

\ Program Files \ apache-Tomcat-6.0.16 \ webapps \ funan_conv. If a file is Loc

Ked, you can wait until the lock times out to redeploy, or stop the Serv

Er and redeploy, or manually remove the deployment at D: \ Program Files \

Pache-tomcat-6.0.16 \ webapps \ funan_conv

Deployment failure on Tomcat 6. x. cocould not copy all resources to D:

\ Program Files \ apache-Tomcat-6.0.16 \ webapps \ funan_conv. If a file is Loc

Ked, you can wait until the lock times out to redeploy, or stop the Serv

Er and redeploy, or manually remove the deployment at D: \ Program Files \

Pache-tomcat-6.0.16 \ webapps \ funan_conv

Solution 1:

Reference

The Tomcat service is not started.

After searching online, I found that I had a problem with everyone. In the original project, I introduced a package. Later, the package was deleted, but this project has been released, therefore, this package name exists in the classpath. In this way, the package will be searched but does not exist during the release, so you cannot copy the package.

Solution: In the Eclipse project, click "right" and select Properties --> the Java build path prompts xx. jar does not exist, so that the jar information can be deleted from libraries. application re-released. Successful!

Solution 2

Reference

The/lib/... in the project under. classpath are all the packages used in our release project. I don't know when to add a few packages. The file is generated under. classpath. Therefore, the project cannot be released at the time of release. One-to-one comparison between packages in. classpath and Web/INF lib

To delete the jar package.

Solution 3

It can be seen that the myeclipse workspace has a problem. Change the workspace! Re-release, OK.