Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334890 - Dangling cross-references do not get fixed
Summary: Dangling cross-references do not get fixed
Status: CLOSED INVALID
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-20 09:43 EST by Mark Christiaens CLA
Modified: 2011-01-20 15:32 EST (History)
2 users (show)

See Also:
sebastian.zarnekow: indigo+

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 Mark Christiaens CLA 2011-01-20 09:43:42 EST 
Build Identifier: 20100917-0705

I have a cross reference that points to the correct declaration.
Then I change the declaration thereby breaking the cross reference. 
Then I change back.  
The cross reference stays broken. 

Reproducible: Always
Comment 1 Mark Christiaens CLA 2011-01-20 09:44:40 EST 
I'm using nightly build 2.0.0.v201101191503
Comment 2 Sebastian Zarnekow CLA 2011-01-20 09:45:49 EST 
Please provide some more information.
Is the referenced element in the same resource? If not, does #isAffected return true after the resource has been changed?
Comment 3 Mark Christiaens CLA 2011-01-20 09:54:23 EST 
(In reply to comment #2)
> Please provide some more information.
> Is the referenced element in the same resource? If not, does #isAffected return
> true after the resource has been changed?

It's on the next line.
Comment 4 Mark Christiaens CLA 2011-01-20 10:01:37 EST 
(In reply to comment #3)
> (In reply to comment #2)
> > Please provide some more information.
> > Is the referenced element in the same resource? If not, does #isAffected return
> > true after the resource has been changed?
> 
> It's on the next line.

BTW I tried to reproduce using the Domain Model example project but that contains errors.  If I remember correctly, I was using a NodeUtil.xxx that didn't exist or something.
Comment 5 Mark Christiaens CLA 2011-01-20 15:32:00 EST 
I'm closing this one.  I think I made a mistake.  I was using a cache for the scoping results.  After some thought, I think it results in stale/inconsistent results.  I've removed my cache and the problem seems to have disappeared.  While I'm at it.  I wonder if the formatting problems I'm seeing are also caused by this ...