75872 – Default IFileModificationValidator that makes files writable

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

Bug 75872 - Default IFileModificationValidator that makes files writable

Summary: Default IFileModificationValidator that makes files writable

Status:	RESOLVED DUPLICATE of bug 28218

Alias:	None

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

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	75854
	Show dependency tree

Reported:	2004-10-08 04:39 EDT by Dirk Baeumer
Modified:	2004-10-08 10:11 EDT (History)
CC List:	2 users (show)

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 Dirk Baeumer

2004-10-08 04:39:14 EDT

3.0

Refactoring calls validateEdit for all files that it is going to modify. If 
the file is under version control and the version control system is integrated 
into Eclipse the Team provider can make the file writeable. However if the VCS 
is "external" the file stays read-only. 

Core resources should provide a default IFileModificationValidator that asks 
the user to make files writeable. This will be active if no team provider is 
present. Additionally the validator could be controlled via a preference.

Comment 1 John Arthorne

2004-10-08 09:43:14 EDT

I thought team already provided a default file modification validator. Michael?

Comment 2 Michael Valenta

2004-10-08 10:07:58 EDT

Yes, Team has a default provider. This problem was fixed in 3.1 M2 (see bug 
28218).

Comment 3 John Arthorne

2004-10-08 10:11:27 EDT

Thanks Michael

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