Bug 359121 - Error indicators in margin incorrect
Summary: Error indicators in margin incorrect
Status: CLOSED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-09-27 13:50 EDT by Mike Norman CLA
Modified: 2011-09-28 10:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Norman CLA 2011-09-27 13:50:22 EDT 
The problem is described on this forum thread:
http://www.eclipse.org/forums/index.php/bm/msg/197480/1/on/0/?SQ=40a0e5cd142a15d5d3497e3efb747201

The problem persists on Indigo SR1 - there aren't any 'real' problems
in the 'Problems' panel at the bottom of the screen, but when editing/browsing
a Java file (in Java/PDE/Debug perspective), a whole bunch of nonsensical
errors are marked in the margin and via 'squiglies'
Comment 1 Dani Megert CLA 2011-09-28 02:38:54 EDT 
Did you do a full build? The Problems view only contains errors after a build took place while the editor reports errors as it gets opened and as you type.

Can you please attach the snippet that produces this?
Comment 2 Mike Norman CLA 2011-09-28 09:40:53 EDT 
Well, that was weird.

I restarted everything from scratch - empty workspace, carefully setting
up my preferences and adding one-by-one my projects (from various repositories:
Orbit support libraries (CVS), EclipseLink (SVN) and misc others (Git - some
local, some at Eclipse Foundation, Github)

and everything works.

I have the 2 workspaces if you wish to compare them? (not attach'd as their
combined on-disk footprint is ~100M)
Comment 3 Dani Megert CLA 2011-09-28 09:45:13 EDT 
> I have the 2 workspaces if you wish to compare them? (not attach'd as their
> combined on-disk footprint is ~100M)

I suspect that it's either a build path issue or that the builder did not run. I suggest to close this bug and reopen if you see this again. We can then look at that workspace.
Comment 4 Mike Norman CLA 2011-09-28 10:08:02 EDT 
I'll do that (and I'll save the broken workspace)