Community
Participate
Working Groups
My projects are scrubbed and rebuilt every time I exit Eclipse and go back into it. This is on RedHat 7.2, GTK 2.0.6. I'm currently running on I20030107 but it was happening on M4 as well. No stack traces are in the log file. My workspace is on a SMB share and I tried recreating it when I was running M4 after I noticed the problem but it didn't make a difference. This problem coupled with the increase of Eclipse lockups (some days it's as often as 1-2 times / hour) is a real productivity killer.
Do any of your projects have major build errors? Use the filter on the task list to see only the problems on the selected resource. If a project has classpath problems or other major build errors, then full builds fail & any small change causes a rebuild.
I had several compile errors but I cleaned them up and it still wants to scrub the output folder and rebuild after starting Eclipse. Once it does the initial rebuild modify / build cycle is fine as long as Eclipse is running.
How many projects do you have in your workspace? Does it affect all of them? Are any stack traces written to the .log file on startup or during shutdown?
Frank: Is this still reproducable? Can you provide anymore insight?
There are no stack traces in the log file. I'm running I20030115 now and it's still happening although it's slightly more bearable as lockups don't seem to be as frequent with I20030115. I have 20 projects and all of them get rebuilt. Is there any way to tell what caused a project to be rebuilt?
But it only happens when you restart your workspace which saved successfully? Or does it only happen after a crash (which is expected beahviour)?
It happens after a successful exit and restart, a crash or the case where I have to kill it (i.e., Eclipse locks up).
Alright let's turn on the builder tracing & see what is happening. Can you please create a .options file in the your eclipse root directory with: # Turn on debug tracing for org.eclipse.jdt.core plugin org.eclipse.jdt.core/debug=true # Reports incremental builder activity org.eclipse.jdt.core/debug/builder=true This is from the .options file in eclipse\plugins\org.eclipse.jdt.core_2.1.0. Then run your workspace with a command line like: d:\R2.0\eclipse\eclipse.exe -debug -consolelog -data d:\R2.0\workspace\plugins - vm d:\jdk1.3\bin\java.exe -vmargs -Xmx150mb Please paste the log (or part of it if its repetitive) into this PR. thanks
I get this for every project: Starting build of Project @ Tue Jan 21 10:37:51 EST 2003 About to read state... Successfully read state for Tomcat About to read state... Successfully read state for Project Binary classpath directory /Tomcat != Binary classpath directory /Project Clearing last state : State for Project (#0 @ Tue Jan 21 10:34:07 EST 2003) FULL build My Tomcat project is referenced directly or indirectly by all of my other projects. It's also the only one that wasn't using src/bin folders. Changing it to use src/bin folders seems to have cleared up the problem.
The build state was correctly written out, but we did not correctly read the project back in as an output folder. thanks Frank.
Verified.
