| Summary: | CVS Decorator causes deadlock during builds | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Tod Creasey <Tod_Creasey> |
| Component: | Team | Assignee: | Platform-VCM-Inbox <platform-vcm-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | jeem, john.arthorne, n.a.edgar, philippe_mulet |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 29192 | ||
|
Description
Tod Creasey
Fix released to HEAD. The CVS decorator will now obtain the workspace lock before obtaining the CVS lock. I'm curious: how are you obtaining the workspace lock? IWorkspace.run? To my knowledge, that is the only way. Is there another way? Not that I know of. But beware that this can trigger an autobuild too. I have run some tests to validate that the autobuild will only be triggered if changes to the resource tree are actually made. We have identified one such case and will modify the code so the resource tree is not effected (see bug 29250). IWorkspace.run is the only way to acquire the workspace lock for a particular duration. I can also confirm that IWorkspace.run will not trigger an autobuild, unless another workspace operation is called from inside the IWorkspaceRunnable. |