- This topic has 8 replies, 2 voices, and was last updated 19 years, 10 months ago by
.
-
Posts
-
Hi
I have 4 projects which I often have to switch between when developing. When switching I close the previous project before opening the new one. The newly opened project often forgets that I have already deployed it to Tomcat and when I go to deploy it again, I get a message saying that the deployment already exists in Tomcat, do I want to delete the existing files, or back then up before deploying. MyEclipse put them there in the first place and are the files that I want to use. I should not have to deploy and overwrite the files each time I open the project. Is the deployment status held in a file somewhere that somehow gets overwritten or what might the reason be that the deploy status gets forgotten. There are a few members of my team who are experiencing the same problem.
We are using MyEclipse 3.8.2 on Windows 2000 with Tomcat 5.0.25.
Thanks
Chris
Chris,
If you search the forums you’ll see there is actually a long discussion about this about a year ago… the Eclipse platform actually specifies a certain behavior w.r.t. to project resources when a project is closed. In Eclipse’s case, its to throw them out which is what MyEclipse honors. You’ll notice your Ant editor/run targets/etc do the same thing (get thrown out) when you close/reopen a project.I agree its annoying, but we are simply honoring the design set forth by the Eclipse team. I do know that this behavior isn’t 100%, and sometimes the deployments will stick around… if this is driving you crazy I can talk with the devs again and see what we can do.
Thanks for your help. It is just that I have to switch between projects regularly and so this behaviour is annoying, so if anything could be done, it would be much appreciated! The projects are quite large and so can take a while to redeploy each time. If the eclipse platform specifies to forget these, maybe there could be an extra option that says to remember deployments, or to have an extra option in the deploy window to ‘attach’ to the already deployed set of files.
Thanks
Chris,
I think this might be fixed in 3.8.3, we added logic to only remove deployments when a project is deleted, and I can’t reproduce “removed deployments” now in my 3.8.3 RC build. So hang tight and let us know if its fixed up when you upgrade.Hi,
I have not had to switch projects since I have upgraded and so have not looked into seeing whether this is okay or not, sorry! I have just starting switching again using 3.8.4 and it still seems to still have the problem.James, try and do this:
1) Remove all your deployments for ALL your projects
2) Close ALL your editors and projects
3) Shut down MyEclipse
4) Add -clean to your command line that you use to start MyEclipse, and start it back up (then you can remove Clean)
5) Open all the projects you were having problems with and rebuild them
6) Re-add the deployments.Does that work? (BTW I still cannot reproduce this: I know this used to be an issue because I was the one that reported it to the team, however they went out of thier way to fix it (keeping the deployments persistent) and I haven’t had this problem since the 2.x series, and I deploy A LOT and always keep my projects closed).
Thanks for your reply. Unfortunately this did not help. I guess I must have an old version of a file somewhere. Maybe a fresh install would do the trick, not that I have time at the moment!
james try this:
1) File > Switch Workspace > C:\tempworkspace (hit OK and let Eclipse restart)
2) Create a new Web Project
3) Setup a deployment, deploy it.
4) Close the project
5) Reopen it, is the deployment still there?
6) Close the project
7) Shut down MyEclipse
8) Fire up MyEclipse, make sure to select the test workspace
9) Open the project
10) Is the deployment still there?
