Bug 140346 - Cannot set build path due to read-only .classpath files
Summary: Cannot set build path due to read-only .classpath files
Status: VERIFIED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.5 M2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-05-05 09:12 EDT by Gunnar Wagenknecht CLA
Modified: 2008-09-15 08:58 EDT (History)
1 user (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 Gunnar Wagenknecht CLA 2006-05-05 09:12:13 EDT 
3.2 RC2

I think this changed somewhere between M6 and RC1. When modifying the build path path of any Java project where the ".classpath" file is read-only I get a pop-up dialog that says something like "I could do nothing, the .classpath file is read-only".

I don't get this message in Eclipse 3.1. IMHO this is a regression because I still know this annoying pop-up from the early Eclipse 2.0 time. 

It looks like the validate-edit is not performed anymore prior to saving the modified classpath.

I think it should work exactly like the Java Editor. It asks if the file should be make writable.
Comment 1 Jerome Lanneluc CLA 2006-05-05 09:18:46 EDT 
I don't think that is a regression. I'm getting the same ".classpath is readonly" error dialog in 3.1.2.
Comment 2 Jerome Lanneluc CLA 2006-05-05 09:25:09 EDT 
I'm also getting the same error dialog with 3.0.2.
Comment 3 Gunnar Wagenknecht CLA 2006-05-05 09:41:46 EDT 
Maybe it's my mistake and it worked due to the ClearCase plug-in.

Right now my environment is different, i.e. I use StarTeam but in another Eclipse installation (due to it's dependencies on 3.1). I don't have the repository plug-ins in 3.2 so maybe that's why it fails to perform an "auto-checkout". Well, there is nothing who could do the checkout.

Anyway, I think JDT should have a story for this, i.e. asking a user if he wants to make the file writable (like the Java editor does).
Comment 4 mminka Mising name CLA 2007-06-04 14:41:55 EDT 
I am getting this on 3.2.2.
It is a signif inconvenience because I can't manually change the .classpath file
(outside of eclipse) 
and do a refresh: the changes aren't read. So the only workaround that 
I have found is to make a new workspace and copy all the projects in with 
the new .classpath. A real hassle.
Comment 5 Jerome Lanneluc CLA 2007-06-11 12:39:29 EDT 
(In reply to comment #4)
> I am getting this on 3.2.2.
> It is a signif inconvenience because I can't manually change the .classpath
> file
> (outside of eclipse) 
> and do a refresh: the changes aren't read. So the only workaround that 
> I have found is to make a new workspace and copy all the projects in with 
> the new .classpath. A real hassle. 
> 
Could you please explain why your .classpath file is read-only ? Are you also using the Clear-Case plug-in and it was not loaded when you tried to modify the build path ?

Also if you are not using a source control plug-in, why can't you change the .classpath to be writable ?
Comment 6 Jerome Lanneluc CLA 2008-08-25 06:00:07 EDT 
(In reply to comment #5)
Please reopen if you have the requested information
Comment 7 Olivier Thomann CLA 2008-09-15 08:58:47 EDT 
Verified for 3.5M2 using I20080914-2000