Bugzilla – Full Text Bug Listing
| Summary: | The javadoc shown by Eclipse is different from what javadoc produces | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Claude Knaus <Claude_Knaus> |
| Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
We are providing all comments in between 2 members, so that the segmented view can perform properly. We only care about the last comment for deprecation check (following the spec). Using the DOM, you can get finer grain information. Ok to close? ok Closing |
20020903-I on w2k and linux-gtk: Consider the following case where two javadocs are following each other. javadoc (the tool) creates html pages with the javadoc immediately preceding the method, while Eclipse shows the first javadoc (e.g. press F2 or hover). IMethod.getSourceRange() returns the source range including both javadocs. I'm not sure if this should be changed to include only the 'last' javadoc, or handled by an entity above which would decide which javadoc to use. ---8<--- public class A { /** * Used by eclipse. */ /** * Used by javadoc. */ public void foo(int value) {} }