Community
Participate
Working Groups
Just guessing that this is due to PDE. Steps: 1. Switch to a new empty workspace 2. Check out org.eclipse.jface and org.eclipse.core.commands from CVS 3. Open TreeViewer.java (-> no error markers in file) 4. Uncheck Project > Build automatically 5. Check out org.eclipse.swt and org.eclipse.swt.win32.win32.x86 from CVS 6. Open Navigator view 7. Rename org.eclipse.swt/.classpath_win32 to .classpath 8. Check Project > Build automatically -> A build is triggered, and you end up with error markers in TreeViewer.java and other files, all over the place. Not sure if these are the minimum steps. This happens a lot to people on the UI team whenever they decide to check out SWT from HEAD into an existing workspace. It is not easy to get things into a proper state again. Sometimes, it helps when you close projects and then open them again. Sometimes, it helps to click the 'Reset' Button on the Target Platform preference page followed by launching an inner Eclipse.
Which build are you using. I just tried these steps on I20071030-0010. The only deviation I made was to use the Package Explorer to change the file name rather than the Navigator view. When I did that, I got 63 warnings in my workspace but not one error.
I just reproduced it with I20071030-0010. Took the SDK build for Windows XP, created a new workspace, and followed the steps. Do you want to watch me (screen sharing) reproducing it? Note that the problems are in the editors, not in the problems view. So I guess I shouldn't have said error markers - you get the red rectangles in the bar to the right of the editor, and red Xs to the left of the editor.
I followed the steps, and then open ActionContributionItem (or MenuManager). The java editor reports everything SWT as an error, even though there are no errors in the workspace. Mine was on linux-gtk I20071030-0010, so the problem isn't OS dependent. PW
I opened an editor on a debug UI class, and all imports in debug.core, jface, and swt were marked with red squiggly's. No errors in the problems view or package explorer. Perhaps this is a Java editor issue?
>Perhaps this is a Java editor issue? Rather a JDT Core reconciler issue then. I'll take a look at this today or tomorrow.
Reproduced with latest, with 3.4M2 and with 3.3. It appears to be a problem in JDT/Core (the project cache might not be reset when the .classpath file is renamed). Moving to JDT/Core for further investigation.
Created attachment 84004 [details] Proposed fix and regression test
Fix and test released for 3.4M4
Verified for 3.4 M4 using build I20071211-0010.
*** Bug 216940 has been marked as a duplicate of this bug. ***
