73381 – Operation on multiple read-only files should prompt to make file writable [general issue]

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

Bug 73381 - Operation on multiple read-only files should prompt to make file writable [general issue]

Summary: Operation on multiple read-only files should prompt to make file writable [ge...

Status:	RESOLVED DUPLICATE of bug 28218

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Resources (show other bugs)
Version:	3.0
Hardware:	PC Windows 2000

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Platform-Resources-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-09-07 11:43 EDT by Nikolay Metchev
Modified:	2004-10-28 16:33 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 Nikolay Metchev

2004-09-07 11:43:04 EDT

If you "Organize Imports" on a bunch of read-only files and the project isn't 
shared the resulting dialog tells you of all the files that were read-only. 
There should be an option to make the files writable and continue with the 
operation.

Comment 1 Dirk Baeumer

2004-09-07 13:09:45 EDT

If we follow that pass we should do it for all actions (Organize imports, 
refactorings, format).

Best would be to have a special "team provider" for this and hook it into 
validateEdit.

To be considered for 3.1

Comment 2 Dirk Baeumer

2004-09-15 13:01:40 EDT

This is not only a JDT/UI issue. All actions that operate on file content 
(Platform/UI, CDT, JDT, WTP,...) should behave the same way then. A special 
team provider would do this for all code manipulation operations that do a 
validateEdit (which should be all of them).

Moving to Platform/Core for comments since such a provider is best provided by 
Core Resources.

Comment 3 John Arthorne

2004-10-28 16:33:42 EDT

This has been fixed in Eclipse 3.1 stream.

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