Bug 126830 - Eclipse cannot save .java files
Summary: Eclipse cannot save .java files
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 1.0   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2006-02-07 17:32 EST by Isidro Gilabert CLA
Modified: 2006-02-10 12:05 EST (History)
2 users (show)

See Also:


Attachments
workspace/.metadata./log (12.01 KB, text/plain)
2006-02-08 14:00 EST, Isidro Gilabert CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Isidro Gilabert CLA 2006-02-07 17:32:04 EST
I cannot save any .java file. I get the message:

Save Failed:org/eclipse/ui/editors/text/TextFileDocumentProvider $FileInfo.fElement

All othe files can be saved .xml .php and so on...
Comment 1 DJ Houghton CLA 2006-02-08 06:37:04 EST
Do you have a Java stack trace in your workspace/.metadata/.log file? Can you attach that here, please?
Comment 2 Isidro Gilabert CLA 2006-02-08 14:00:00 EST
Created attachment 34363 [details]
workspace/.metadata./log

Here it is the log file, thanks in advance.
Comment 3 DJ Houghton CLA 2006-02-08 14:16:44 EST
Looks like a dup of bug 104486. 
Moving to JDT/Core for comment.
Comment 4 Olivier Thomann CLA 2006-02-08 14:28:51 EST
Could you please specify what build you are using?
Comment 5 Isidro Gilabert CLA 2006-02-08 14:40:22 EST
I think I found what is happening...

I switched to Sun's Java instead of kaffe and now it works perfectly.

Thanks everyone!

Is it kaffe's fault?
Comment 6 Jerome Lanneluc CLA 2006-02-09 10:42:50 EST
The save failed because of an IllegalAccessError (see attached .log file) and not because of a JavaModelException.

It looks like a runtime issue. CompilationUnitDocumentProvider doesn't have access to field fElement of TextFileDocumentProvider$FileInfo.

Moving to Platform Runtime for comment
Comment 7 John Arthorne CLA 2006-02-10 12:05:46 EST
It looks like a VM issue.  It is reporting illegal access in the case of a field on a protected nested class in the superclass.  The Eclipse Java compiler, and the Sun VM, don't report this as an illegal access.