Bugzilla – Full Text Bug Listing
| Summary: | Use Javadoc @deprecated for code repair proposal | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ulrich Windl <Ulrich.Windl> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, jesper |
| Version: | 4.7.3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Hi Ulrich - this is very difficult to implement in general, since A) the text in the JavaDoc need not follow any known grammar, and since the new method being referred to often take different arguments, have a different base type. Moving to JDT UI (as it's not an APT problem) |
(I'm new to Eclipse and java, so maybe I don't know the correct phrases) If I @Deprecate a used method, also adding a @deprecated comment, Eclipse complains that I'm using a deprecated variable (in my case), and it displays the @deprecated message that suggests the replacement, but Eclipse seems unable to extract the info from the doc to suggest a code fix. A code fix proposal would be nice, however... I'm talking about a comment like "@deprecated use {@link #tail()} instead.". Here I'd expect that Eclipse suggests a replacement for the deprecated variable with tail().