Summary: | Better location for deprecated type warning message | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, jerome_lanneluc, philippe_mulet |
Version: | 3.3 | ||
Target Milestone: | 3.6 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Olivier Thomann
2007-01-09 13:29:08 EST
This is a duplicate of bug 132677 which originally only asked to improve the deprecation problem range and then got generalized. I would like to see this (the deprecation case) fixed because we could then go ahead and improve Javadoc hovers: currently we show the problem message for deprecated code. Unfortunately the problem text isn't a big help i.e. doesn't tell you what to do. I would like to show the Javadoc of the deprecated element in this case. This is currently hard because the problem range is too big. If the range would be reduced to the name range (so that it matches codeSelect behavior) I could make this happen. I know that I should close them the other way around, but bug 300031 is already in the buildnotes. *** This bug has been marked as a duplicate of bug 300031 *** |