Community
Participate
Working Groups
At some point during development of Java code I get a set of problems. - a previously OK class gets flagged with multiple errors at the class level, with no individual errors in body of class, the only solution I've found is to delete and recreate the class. With the same content the class is now OK. - connected to this (I think), the Editor loses the ability to copy text. Upon the attempt to do so a message dialog appears with the message that includes "Save could not be completed" "org.eclipse.jdt.internal.compiler.lookup.FieldBinding" I believe this FieldBinding is involved in the other problem as well, but I haven't been that diligent in recording the information - sorry. This first appeared using 3.1M4. I've downloaded 3.1M5 - Mar. 2 - and started up the M5 installation this morning and created a new project in a new workspace pointing at the existing code, thinking that the M4 workspace had a problem. The problem till appeared. In order to keep working, I copied the Java file, deleted the class within Eclpise, created a new class with the same name, and copied the contents from the copy of the original fine using the Eclipse editor, and everything's OK. FWIW, I've had (similar?) problems with 3.1 where problems lingered until I either did the copy file / delete class / recreate class, or went into the workplace and found and removed stuff from the plugins files. Again, sorry I didn't keep track of what I was doing in the rush to get things working. I'll keep better track in the future. it's still here. Sorry, but
Please provide the contents of your .log file in the .metadata folder of your workspace.
Created attachment 18521 [details] Eclipse .log file contains stack trace showing same text as the dialog in the editor - "org.eclipse.jdt.internal.compiler.lookup.FieldBinding" I was asked to send the log file, forget by whom.
Could you also attach the original source which made the problem occur to start with ?
(In reply to comment #3) > Could you also attach the original source which made the problem occur to start > with ? I'll along the code to the specific class where the problem shows up. It's not very pretty. I'm not sure about sending all the code - there are likely some proprietaty restrictions & I'm not eager to run afoul of them. FWIW, the problem just showed up again immediately after adding: implements Comparable, Serializable { static final long serialVersionUID = 1; to ANOTHER class. Seems odd to me.
Created attachment 18806 [details] Class manifesting bug
Dup. Should be addressed in today's integration build. Please reopen if you see it again. *** This bug has been marked as a duplicate of 87490 ***
