Bug 4331

Summary:	Updating a Read-only .classpath file does not warn the user that the update did not happen (1GLEVO4)
Product:	[Eclipse Project] JDT	Reporter:	Erich Gamma <erich_gamma>
Component:	UI	Assignee:	Martin Aeschlimann <martinae>
Status:	VERIFIED FIXED	QA Contact:
Severity:	critical
Priority:	P3
Version:	2.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Erich Gamma

2001-10-10 23:09:55 EDT

1) Create two Java projects  Project1  and Project2
2) Make the .classpath file for  Project1 read-only  (RMB on .classpath file, 
choose Properties, check read only)
3) Update Project1's Java Build Path to include Project2  (RMB on Project1, 
choose Properties, choose Java Build Path, choose Projects tab)
4) To the user it looks like this has occurred without problem (it's still in 
Project1's Java Build Path, and calls to the JavaModel return the correct 
information)
but since the .classpath file is read-only, this change has never occured).  At 
this point we believe the user should have been told that the
file could not be updated.
5) Bring down the workbench and bring it back up, and it is no longer in  
Project1's Java Build Path.

They need a message to remind them that they need 
to check out the .classpath file.

NOTES:

Comment 1 Dirk Baeumer

2002-01-08 08:12:25 EST

Martin, please investigate if we swallow an exception or if Core doesn't handle 
this case.

Comment 2 Martin Aeschlimann

2002-01-11 10:02:27 EST

cant reproduce in 20109: When trying to change the classpath and pressing OK, a 
error dialog comes up and reports about the read-only state.