Community
Participate
Working Groups
Kepler. When saving many files (30), it is clear from the progress and generally incredibly slow progress, that the 30 files are not saved as a group. Rather each is saved individually provoking many individual builds with all the consequent project updates. Very very inefficient, and I think a regression compared to 3.x
I tried to reproduce it, but always got only one build request so far. If you still see this, please start Eclipse with -debug <file>, where the file has the following debug options: org.eclipse.core.resources/build/invoking=true org.eclipse.core.resources/build/delta=true org.eclipse.core.resources/build/needbuild=true org.eclipse.core.resources/build/needbuildstack=true org.eclipse.jdt.core/debug=true org.eclipse.jdt.core/debug=true org.eclipse.jdt.core/debug/builder=true org.eclipse.jdt.core/debug/builder/stats= true This will show what the builder actually does and why it gets triggered.
Are the files you are saving subject to EGIT analysis for entry to the Staging View?
(In reply to comment #1) > This will show what the builder actually does and why it gets triggered. Where? I've tried a variety of "> log.log" additions to the command line, but they variously give me a strange "No exit data" pop up or nothing to see.
(In reply to comment #2) > Are the files you are saving subject to EGIT analysis for entry to the > Staging View? No - nothing in the bug report mentioned EGit. If you can provide more details about your steps, it might help. But having the traces should be enough. (In reply to comment #3) > Where? I've tried a variety of "> log.log" additions to the command line, > but they variously give me a strange "No exit data" pop up or nothing to see. The debug info is written to the console which launches Eclipse. You need to use eclipsec.exe which connects the Eclipse console with the host console. Also, since there will be lots of logging, you want to redirect to a file by appending the following to your command line: > log.txt 2>&1 Please also add the following two options to the options file: org.eclipse.core.resources/debug=true org.eclipse.core.resources/build/stacktrace=true
(In reply to comment #4) > The debug info is written to the console which launches Eclipse. You need to > use eclipsec.exe which connects the Eclipse console with the host console. > Also, since there will be lots of logging, you want to redirect to a file by > appending the following to your command line: > > log.txt 2>&1 Can you please provide a command line that works. With eclipsec at least a console appears, but is shows that the redirection is swallowed by the workspace! I'm using C:\Tools\Eclipse\4.3RC4\eclipsec.exe -debug Temp/debug.txt -data C:\Development\Buck\Workspace4.2 -vm "%JAVA_HOME%\bin\javaw.exe" > Temp/log.txt 2>&1 but the console shows me -debug Temp/debug.txt -data C:\Development\Buck\Workspace4.2 > Temp/log.txt 2>&1 -vm C:\Program Files\Java\jdk1.7.0_25\bin\javaw.exe
(In reply to comment #5) > (In reply to comment #4) > > The debug info is written to the console which launches Eclipse. You need to > > use eclipsec.exe which connects the Eclipse console with the host console. > > Also, since there will be lots of logging, you want to redirect to a file by > > appending the following to your command line: > > > log.txt 2>&1 > > Can you please provide a command line that works. With eclipsec at least a > console appears, but is shows that the redirection is swallowed by the > workspace! > > I'm using > > C:\Tools\Eclipse\4.3RC4\eclipsec.exe -debug Temp/debug.txt -data > C:\Development\Buck\Workspace4.2 -vm "%JAVA_HOME%\bin\javaw.exe" > > Temp/log.txt 2>&1 > This can't work because javaw.exe explicitly runs without console (window). You need to use java.exe. eclipsec.exe -debug c:\eclipse\.options -data %TARGET% -vm %SDK% -vmargs %VMOptions% %* > log_tmp.txt 2>&1 works for me.
Ed, any news on this?
(In reply to comment #7) > Ed, any news on this? Redirection to a file doesn't work so I only get to see a thousand lines of console and it all scrolls past quite fast when anything relevant might be happening. But I would have to suspect that when watched, it is much better behaved. Within my limited understanding of the messages they seem plausible.
Created attachment 234708 [details] Debug log of suspect behaviour I think I got one. The attached resulted from doing a Search during a JUnit test, with the Search needing to do some saves so it was all slow. In the Progress View I was able to sit watching the irritating Building 50% complete while Saving Modifications was waiting. If there are modifications to save then the build should be aborting. In the attached, searching for org.eclipse.ocl.examples.build finds a project with many builders and dependencies. org.eclipse.qvtd.build has even more dependencies.
The suspect log was using platform Version: 4.4.0 Build id: I20130820-0800 with M1 contributions for most other things.
Created attachment 234713 [details] 7 file multi-build A much clearer example. Seven Java files were dirty in org.eclipse.ocl.examples.build when I did a Save All. The changes were addition of @Override after a change from Java 5 to 6 BREE, which had already prompted rebuilds to indicate the need for edits.
OK, I see it now. It's not just a 4.x problem but happens when the system is slow enough, so that the auto-build requests issued by each save aren't grouped into one anymore.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
