Bugzilla – Full Text Bug Listing
| Summary: | Java stack trace console should offer choices when multiple times the same qualified name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | remy.suen | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
This is really a workflow/usability issue. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Created attachment 185429 [details] Error dialog open once the .class file editor is opened I have a case where I have a version of JDT/Core that comes with the jasper bundle. So I have more than once types with the same qualified name on the search path. I got a stack trace that involved types inside jdt/core. When I click on the link to get to the corresponding source file, in my case, the .class file from the jasper bundle is open using a class file editor with an error dialog about a wrong line number. Of course if a class file editor is open, the corresponding line number won't match. When the same type (same fully qualified name) is found multiple times, I think the java stack trace console should offer a dialog to select the one I want. Opening a .class file will fail for sure and there is no workaround as I cannot figure out how the type from jasper is found. So right now this makes this console unusable for me when it is about opening any type inside the jdt.core bundle.