75854 – Refactoring against read-only files

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

Bug 75854 - Refactoring against read-only files

Summary: Refactoring against read-only files

Status:	RESOLVED DUPLICATE of bug 28218

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.0
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	JDT-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:	75872
Blocks:
	Show dependency tree

Reported:	2004-10-07 17:05 EDT by CW Renniks
Modified:	2004-10-08 10:41 EDT (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description CW Renniks

2004-10-07 17:05:20 EDT

It would be great when doing a rename or move refactor that files that show up 
as read-only, could be quickly and easily made writable from within the 
preview dialog. Currently, and especially tedious when working against a VCS 
that makes file read-only, this is very tedious.

Comment 1 Dirk Baeumer

2004-10-08 04:22:01 EDT

The workbench provides a hook to make fils writeable if the are readonly. 
Refactoring is calling the hook. Is you VCS system integrated into Eclipse ? 
If so they have to implement the hook to make the file writeable.

Comment 2 Dirk Baeumer

2004-10-08 10:41:36 EDT

Got fixed for M2 by bug 28218.

*** This bug has been marked as a duplicate of 28218 ***