Bug 59450 - Vaildate Edit before .classpath change?
Summary: Vaildate Edit before .classpath change?
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-21 11:16 EDT by Michael Valenta CLA
Modified: 2004-05-12 11:30 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 Michael Valenta CLA 2004-04-21 11:16:38 EDT 
I am at a code camp and, while using the ClearCase plugin, we tried to 
associate source with a plugin from the install. For some reason, this tried 
to update the .classpath file (not sure why this is required). However, the 
update of .classpath failed because the file was not checked out. After manual 
checkout, the file was editable. However, if validateEdit was called, this 
manual checkout would not have been required. Does JDT Core perform a 
validateEdit before modifying the classpath file?
Comment 1 Michael Valenta CLA 2004-04-21 11:18:11 EDT 
We were using M8
Comment 2 Philipe Mulet CLA 2004-04-23 09:19:09 EDT 
Yes we do (JavaProject#setSharedProperty) if the .classpath file exists and is 
read-only.
Need to be reproduced.
Comment 3 Jerome Lanneluc CLA 2004-05-12 11:30:42 EDT 
Verified that we do a validateEdit(...) on the IFile representing 
the .classpath if it exists and it is read-only.
Please reopen if you see this problem again and have steps to reproduce.