Description Robert Wloch 2010-05-13 15:02:06 EDT

Created attachment 168443 [details]
error appears in runtime workspace using default encoding which is a custom encoding in development workspace

While testing some modeling plugins in a runtime workspace I discovered, that Eclipse doesn't list all files in Project and/or Package Explorer. It skips files with German umlauts (ä,ö,ü). It seems that the resource code is not even aware of these files. I checked that using workspace.findMember() in combination with a resource visitor.

This issue might also be connected to the PDE but I'm not sure about that.
Creating files with umlauts will actually create them on the file system, but the editor in Eclipse will open with a FileNotFoundException. As you can see on the screenshots, the Project Explorer is showing the file. However, as soon as I refresh the workspace it's gone but still lives on on the file system. Further refreshs will not make such files appear again.

The bug is reproducible and exists already in Eclipse 3.5. I tested it with modeling SR2 and modeling 3.6M7. I failed to reproduce it on my Windows box. So it might be connected to Linux and maybe even to Linux using utf-8 as default file encoding.

Here is a guide to reproduce it:
1) Download and unzip fresh Eclipse.

2) Start it and create a new workspace.

3) In that workspace create a general project "foo" and add a file "bäd.txt". It will always work in the development workspace.

4) Delete the file.

5) In the workspace preferences change the encoding from utf-8 to something else than that default, e.g. to iso-8859-1.

6) Create the file "bäd.txt" again and note that it's still working: I never had problems in development workspaces.

7) Delete the file.

8) Create a new run configuration for an "Eclipse Application" and launch it.

9) In the runtime workspace check the workspace encoding in the preferences: The workspace encoding is set to default which uses the encoding of the development workspace, that was set to a custom encoding in step 5).

10) Create a general project "foo" and create a file "bäd.txt" in it. The default editor will show a FileNotFoundException.

11) Delete the file. If you don't and you refresh it'll not be shown in the Project Explorer any more and you'll need to delete it outside of Eclipse.

12) Still in the runtime workspace, change the workspace encoding to whatever is the default of the development workspace. (In my case, the default of my development workspace is utf-8. So, I set "utf-8" as custom encoding in my runtime workspace.)

13) Create the file "bäd.txt" again and note that it's still NOT working.

14) Delete the file.

15) Close the runtime workspace.

16) In the development workspace change the workspace encoding back to its default.

17) Start the runtime workspace.

18) In the runtime workspace set the workspace encoding in the preferences to default which uses the encoding of the development workspace. (In my case the default is utf-8.)

19) Create the file "bäd.txt" see that it's working this time.

20) Delete the file.

21) Still in the runtime workspace, change the workspace encoding to something else. I set it to "iso-8859-1".

22) Create the file "bäd.txt" see that AGAIN it's working this time.

I suppose this does not only affect German umlauts, but any letter that is not part of the english alphabet, but I've not tested that.

This issue might also be connected to the PDE and the mechanism behind starting a runtime workspace but I'm not sure about that.