Summary: | General failure of functionality | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Chris Gerrard <chris> | ||||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||||
Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | ||||||||
Version: | 3.1 | ||||||||
Target Milestone: | 3.1 M6 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Chris Gerrard
2005-03-02 11:12:00 EST
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
|