Community
Participate
Working Groups
Build ID: I20080502-0100 Steps To Reproduce: 1. Open Eclipse with some projects already open (I had 65 open, from the project Archimedes - the open CAD) 2. Wait for the compiler to start building the workspace More information: When Eclipse starts building the workspace, the following error message is sent to console: Exception in thread "Compiler Source File Reader" org.eclipse.jdt.internal.compiler.problem.AbortCompilation at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:81) at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:151) at java.lang.Thread.run(Thread.java:619) Exception in thread "Compiler Source File Reader" org.eclipse.jdt.internal.compiler.problem.AbortCompilation at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:81) at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:151) at java.lang.Thread.run(Thread.java:619) I have already tried to refresh and clean the project, but it still continues. It is not specific for one project.
Did not happen after rebuilding projects inside Eclipse 3.3
Could be an encoding issue surfacing, but mishandled in concurrent compiler.
Please try a recent nightly build. We released a fix for bug 229480, so we should get better error reporting from now on. thx
I've thrown some exceptions from SourceFile.getContents() & with the fix for bug 229480, we're correctly reporting them as build errors. I suggest we close this as WorksForMe, unless Luiz can confirm that he still has a problem with the lastest build.
(In reply to comment #4) > I've thrown some exceptions from SourceFile.getContents() & with the fix for > bug 229480, we're correctly reporting them as build errors. > > I suggest we close this as WorksForMe, unless Luiz can confirm that he still > has a problem with the lastest build. > I will download the latest Integration version tomorrow and try to reproduce the bug. Another detail that may be relevant is that I had updated the projects outside Eclipse (by 'svn update') before that bug appeared. Before that, it was working normally for me.
I couldn't reproduce the bug neither in build I20080513-2000 nor in the build I20080502-0100, which was the build with that bug originally. I think it may happened for a specific update for the project which I was working on.
Might want to keep this bug open until 3.4 end...
Kent, please close early 3.5 if it still cannot be reproduced.
Reducing severity, since it cannot be considered as a blocker if not reproduceable any longer.
We believe this was fixed 2 months ago with the change for bug 229480 (released in 3.4 RC1) & have not received any similar bug reports since then.
Verified for 3.5M1 using I20080805-1307