Bug 6165

Summary:	handle read-only class path file in a graceful way
Product:	[Eclipse Project] JDT	Reporter:	Erich Gamma <erich_gamma>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P2
Version:	2.0
Target Milestone:	2.0 M6
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Erich Gamma

2001-11-21 10:19:31 EST

JDT Silently looses changes to readonly .classpath file.

this isn't a new problem, we should address this in 2.0.

CORE should throw an exception in this case.

Comment 1 Philipe Mulet

2001-11-26 13:01:47 EST

What about the complaint against the JavaModel notifying the impossibility of 
changing the content of a read-only file (bug 4210) ? 

We should be consistent and either always fail or always ignore. Failing seems 
appropriate and goes in the direction suggested by this bug report.

Comment 2 Erich Gamma

2001-11-26 13:28:38 EST

I expect some changes with regard to handling read-only files. This is 
triggered by requirement to support pessimistic VCMs. These systems have their 
files read-only when they are not checked out.

Comment 3 Erich Gamma

2002-02-13 01:46:19 EST

FYI, the API call to use before modifying a file is validateEdit provided by 
the Workspace.

Comment 4 Philipe Mulet

2002-04-23 08:41:48 EDT

Fixed along with bug 13905

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