Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369432

Summary:	Loss of edits if remote workspace is disconnected
Product:	[Eclipse Project] Platform	Reporter:	Physix <mrb.physix>
Component:	Text	Assignee:	Platform-Text-Inbox <platform-text-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, remy.suen
Version:	3.8
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	93562
Bug Blocks:

Description Physix

2012-01-23 13:34:08 EST

Build Identifier: Version: 3.7.1 Build id: M20110909-1335

If editing project files stored on a remote workspace (such as on a network drive)  and the drive is disconnected the only options available are to close the files or attempt to relocate the project directory.  There is no option to save the file locally or even simply to close the dialog box to allow a copy paste into a different window, even though the text on the screen must be cached locally.

Requested fix: provide an option to either "Save A Copy" or "Take No Action" upon getting disconnected from the remote workspace.

Reproducible: Always

Steps to Reproduce:
1. Create a remote workspace on a mapped network drive
2. Create a project in the remote workspace
3. Open a file and make edits
4. Disconnect from network drive (change networks, turn off network connection, etc.)

Result: Dialog box with 2 options opens, save, or close.

Save: Save As is limited to workspace, however the workspace is no longer connected and there are no options to browse to a different file system location.

Close: closes the editor which eliminates all changes, killing the ability to copy and paste the file into another text editor application.

Comment 1 Lars Vogel

2019-11-14 03:29:38 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.