For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 10 replies, 5 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
I am using eclipse 3.1M7 with myeclipse 3.8.4.
I’ve noticed this many times, but for some random reason myeclipse loses the j2ee deployments I have setup. I have to redeploy my applications.
Try and nail down the exact use case that causes it, this is an old subject from a while back that we spent about a month banging on with many users helping us and finally got it fixed (According to Eclipse design doc deployments and other project-specific resources should be ‘cleared’ when a project is closed, this was the most likely cause of the removal of deployments) but we purposefully persisted them even when a project was closed at user demand.
I’m facing the same issues.
I could live with the fact that deployments are always lost after closing a project. However, in the current situation sometimes deployments are lost after closing a project and sometimes not. It seems to happen a bit more often when I close all my J2EE projects, and then opening one. In contrast, when I instead open a previously closed J2EE project first and then close another J2EE project, loosing the deployment happens less often.
Sorry for not giving the environmental details. I’m using MyEclipse 3.8.4 on Eclipse 3.02, JDK1.5_03 on Debian GNU/Linux which is regularly updated. My co-developper experiences the same problems, he’s using 3.8.3/3.02 but uses the IBM 1.4.2 JDK on Debian GNU/Linux for AMD64. So, no RC- or M builds involved here.
It’s not really a very severe problem, as deployments typically don’t get lost all of sudden (as they used to in the ‘old’ days), but mostly after a project open/close operation.
If you can nail down exactly a case where they ARE removed, I will test the heck out of it. But as I mentioned when this was a hot topic (I originally asked the team for this fix cause I always close my projects) it took me 2 weeks and I was never able to find a reproduceable case, so they went in and added some persisting code that should make the deployments live forever and it fixed it for us… so if it is still popping up we really need a working test case to figure out what is going on.
I don’t do anything except open/close eclipse. It’s completely random. I never close my J2EE project. Sometimes I close unrelated projects, but that doesn’t seem to be related.
It may be unrelated to MyEclipse since the “Problems” view is also reset when this happens.
this happens to me too, quite often (at least once a week). it’s sporadic, mostly after eclipse close & open. but iirc it happened also 2-3 times after project only close & open (3-5 open projects). worst case was last week when i saw the debugger step in comment lines between methods. imagine my surprise 😉 took a while to notice that the deployment was gone…
E 3.0.2 + ME 3.8.4 + QF2, JRE 1.5.0_03, JDK 1.4.2_x & 1.5.0_03, currently using only Tomcat 5 deployment (2-3 parallel webapp deployments).Guys can you hang tight for our 4.0 release and see if this is still happening? I’m curious if the move to 4.0 as well as the Eclipse 3.1 platform could impact this persistence issue.
Riyad, and when will ME 4.0 release be out? Are you waiting for E 3.1 to be relased? Can you promise it won’t take longer? … Or will at least ME 4.0 RC2 then be stable enough ?
