| Summary: | Dangling cross-references do not get fixed | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Mark Christiaens <mark.g.j.christiaens> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mark.g.j.christiaens, sebastian.zarnekow |
| Version: | 2.0.0 | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | M5 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Mark Christiaens
I'm using nightly build 2.0.0.v201101191503 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? (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. (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. 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 ... |