| Summary: | Workspace source look up rule conflict | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Pawel Piech <pawel.1.piech> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | grant_gayed, pawel.1.piech, thatnitind | ||||
| Version: | 3.7 | Flags: | Michael_Rennie:
review+
|
||||
| Target Milestone: | 3.7 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=578709 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Rennie
I guess our solution to serialize the source lookup operations jobs was a little too simplistic. We have to assume that source display could touch (or open as is the case here) any resource in the workspace. I guess that would be the IResourceRuleFactory.buildRule()? Created attachment 190957 [details] Patch to use the build rule in source lookup. This patch changes the source lookup job to use the buildRule(). It may have the weird side effect that source lookup will be delayed until a running build is completed. The alternative is to forbid modifying resources during source lookup, which is not backward compatible in this case. Or we could back out our partial fix for bug 327497. Mike reported that use of build rule resulted in deadlocks... not good :-( So I reverted the use of scheduling rule in source lookup job. Mike, please verify. looks good. |