Bug 14229

Summary:	Failure writing to a read only .project
Product:	[Eclipse Project] JDT	Reporter:	Josh Heidebrecht <jheidebr>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.0 M6
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Josh Heidebrecht

2002-04-19 11:10:02 EDT

build M5:

Changing a Project's Java build dependencies by adding/removing a project on 
the build path does not report a file write error. During the add/remove if 
the .project file is read only it is not modified nor is an error dialog 
reported.

Comment 1 Philipe Mulet

2002-04-23 07:35:05 EDT

Fixed this scenario by triggering the project reference update before modifying 
the actual classpath. If it fails, the classpath setting is not performed at 
all.

However, identified a bug in the platform, if an exception occurs during 
the .project file writing, the project references are left inconsistent in 
memory (see bug 14396).

Fixed for the JDT/Core part, bug 14396 describes the Platform/Core part of this 
defect.