Bugzilla – Full Text Bug Listing
| Summary: | In certain situations, class lookup fails for classes with dollar sign in their name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Eric Bodden <eric> | ||||
| Component: | Core | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | stephan.herrmann | ||||
| Version: | 4.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Hi Eric, I hope you don't mind me closing this as a duplicate of the other bug :) *** This bug has been marked as a duplicate of bug 401952 *** Oh, weird... Id did have trouble submitting the report but I did not realize that the system had created two separate reports. So thanks! |
Created attachment 227692 [details] Screen shot I and others have observed a problem with the way Eclipse resolves classes that have a dollar sign in their name. I get errors such as "ASTNode$State" although the class clearly exists. The code compiles just fine with javac. We encounter such class names in auto-generated code. The bug does _not_ seem to manifest with Eclipse versions predating the 4.x stream. Unfortunately, this problem occurs in a larger project in which we have a rather large set of generated classes. I tried to cut down the problem size to create a smaller error report for you but that appears to be quite hard, as often this causes the incorrect error message to mystically disappear. With the full project, the error is completely reproducible, though. I am therefore attaching a screenshot and the complete project as a ZIP file. I hope that will help with debugging.