Bug 152 - Resource History: ignores read-only (1GF0IHC)
Summary: Resource History: ignores read-only (1GF0IHC)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Michael Valenta CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 21:37 EDT by Jean-Michel Lemieux CLA
Modified: 2002-04-26 16:03 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michel Lemieux CLA 2001-10-10 21:37:18 EDT
Add to Workspace overwrites read-only

1. For a versioned project, make it and its files read only
2. Do Show in Resource History to it
3. In the resouce history, do Add to Workspace.
4. The dialog asks whether to overwrite the existing project. Click yes( not yes to all )
	Notice that it doesn't confirm you for its read only files and goes on to overwrite 'em all
	It also changed the states of all the files in the project to NOT read only

NOTES:
Comment 1 DJ Houghton CLA 2001-10-23 23:44:41 EDT
PRODUCT VERSION:
120 JDK
Windows 2000

Comment 2 Michael Valenta CLA 2002-03-28 10:12:09 EST
Fixed
Comment 3 Jean-Michel Lemieux CLA 2002-04-10 12:42:49 EDT
Doesn't work for me. The file was overwritten.
Comment 4 Kevin McGuire CLA 2002-04-10 16:25:10 EDT
It *should* overwrite managed read-only files, with whatever read-only status 
the file had when committed.

Confirmed that:
- it overwrites read-only
- but leaves the file writeable

In this test case, both the local and repo versions of the file were read-only, 
and the result writeable, which is bad.
Comment 5 Michael Valenta CLA 2002-04-26 16:03:13 EDT
For Replace with Revision, an update is performed which will overwrite read-
only files and set the permissions as directed by the server. 

Replace with Contents will invoke the validateSave which will report that the 
file is read-only