Bug 14229 - Failure writing to a read only .project
Summary: Failure writing to a read only .project
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-19 11:10 EDT by Josh Heidebrecht CLA
Modified: 2002-04-23 07:35 EDT (History)
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 Josh Heidebrecht CLA 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 CLA 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.