| Summary: | Unhelpful error message when deleting project (1GDQ11R) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Nick Edgar <n.a.edgar> |
| Component: | UI | Assignee: | Knut Radloff <knut_radloff> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | usability |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M6 | ||
| Hardware: | All | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Nick Edgar
PRODUCT VERSION: 104 VAJ Pls include this in your "Improved Servicability" task. The exception returned by Core (with the message "problems deleting resources") is a multistatus. The children of the multistatus indicate that there are files out of sync with the filesystem. This is indicated by the status code of IResourceStatus.OUT_OF_SYNC_LOCAL, and by a message to the user. In build 20020125, this information is correctly revealed in the UI if the user clicks on the "Details" button. So it looks like the main servicability problem has been addressed since this PR was entered. For a nicer user experience, the UI should detect the OUT_OF_SYNC_LOCAL case, and then prompt the user with something like "The project has changed in the filesystem since the last refresh. Delete anyway?" If the user clicks yes, then call delete a second time with force=true. This will force deletion regardless of whether the filesystem is out of sync with the workbench. I wouldn't recommend forcing deletion without user interaction, because files may have been added in the filesystem that the user forgot about. Silently forcing deletion in that case could mean lost work. Moving to UI for consideration. Filed separate bug 8592 for review of how we handle out of synch resources. This scenario works, presumably because the workbench is passed the refresh from local command line parameter. In addition, the new "Delete project contents" prompt always forces deletion when the project content is deleted and a contained resource is out of sync. |