Summary: | Attached source not shown for classes in JAR | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Michael Fraenkel <fraenkel> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Michael Fraenkel
2002-01-15 14:16:56 EST
There seems to be a dependency on certain debugging info to make the Source Attachment stuff works. If you compile with -g:none, Source Attachment doesn't work. Sounds like you are relying on -g:source info to be present. Seems like you can do better with the information you have just on the fully qualified class name. The trick is that the source name as encoded in the classfile is the only legite information to present to a user (the one the debugger will present). Secondary types cannot be inferred the name of their compilation unit. We could introduce a smart heuristic in case there is no source info in the classfile, but will consider it only post 2.0. Reopening |