- This topic has 8 replies, 4 voices, and was last updated 21 years, 2 months ago by
.
-
Posts
-
I have a web application that I’m trying to deploy onto Tomcat 4.1.30. When I go to deploy it through the Project Deployments icon on the toolbar, it tells me that another project has already been deployed with the same context name. However, I had deleted that project a while ago and restarted the server a few times since. Can someone tell me how to clean out whatever setting is getting in the way? Thanks
Brian
If you are doing an exploded deployment, then you need to go to the location that you see in the deployment destination box, and erase that directory (or just hit the “Remove” button and the deployment tool will remove it for you.
If you are doing a packaged deployment, then you need to remove the WAR file (not just the directory). again, the deployment tool will do this for you if you click “Remove”. Make sure to have Tomcat shutdown when you do this, because on Windows it has a tendency to lock the files, so a delete operation will usually fail (annoying but nothing we can really do about it).
Problem is that the directory is not there. When I had problems, I completely reinstalled Tomcat. The deployment manager still thinks it is there. Is there a configuration setting somewhere that contains information about where the webapps are deployed in Tomcat?
ive had this same problem, except an enterprise app on jboss. the problem started when i manually removed the directory (exploded deployment) instead of removing it through the myeclipse deployment manager. restarting jboss, and eclipse, and reinstalling jboss all did nothing. the problem didnt go away until i reinstalled eclipse/myeclipse.
Brian,
What version of MyEclipse are you using? There was a lot of work done to that area of the deployer in the 2.7 release so I need to verify if this is a new issue or a fixed one.
However, to get moving again quickly you’ll find that the deployments are stored in:
<workspace>\.metadata\.plugins\com.genuitec.eclipse.ast.deploy.core_<version>\prefs.iniI ended up reinstalling with the newest version of the software so I’m not sure what I had before. I downloaded the version with which I had the problem sometime in April though. Hope that helps.
Thanks for the info about where the deployment info is stored though. Hopefully I won’t have to use it in the future, but it’s nice to know in case I do. Thanks for being responsive guys.
