Description Justin Berstler 2009-04-28 15:38:20 EDT

Build ID: I20090202-1535

Steps To Reproduce:
The scenario is that the user has all the project metadata files under .settings checked in by a read-only source control system.  Some client code is calling File#setCharset on a file inside this project, which would like to write to org.eclipse.core.resources.prefs to store the encoding.  However, the user is never prompted to checkout this file and as a result the edit fails silently except for the following stack trace in the .log:

!MESSAGE Exception occurred while saving project preferences: /project/.settings/org.eclipse.core.resources.prefs.
!STACK 1
org.eclipse.core.runtime.CoreException: No files were checked out.
	at org.eclipse.core.internal.resources.ProjectPreferences$2.run(Unknown Source)
	at org.eclipse.core.internal.resources.ProjectPreferences.save(Unknown Source)
	at org.eclipse.core.internal.preferences.EclipsePreferences.flush(Unknown Source)
	at org.eclipse.core.internal.resources.ProjectPreferences.flush(Unknown Source)
	at org.eclipse.core.internal.preferences.EclipsePreferences.flush(Unknown Source)
	at org.eclipse.core.internal.resources.ProjectPreferences.flush(Unknown Source)
	at org.eclipse.core.internal.resources.CharsetManager.setCharsetFor(Unknown Source)
	at org.eclipse.core.internal.resources.File.setCharset(Unknown Source)

This scenario can be reproduced by checking in the .settings/org.eclipse.core.resources.prefs file with a source control system like ClearCase, or by using the Pessimistic Filesystem Provider included in the Eclipse example plugins.


More information:

Also see Bug 149190 and Bug 190268 for eerily similar scenarios.