JDK-8198890 : The standard doclet incorrectly produces wrong method signatures in certain cases.
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • CPU: generic
  • Submitted: 2018-03-01
  • Updated: 2018-05-01
  • Resolved: 2018-04-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11
11 b11Fixed
Related Reports
Duplicate :  
Relates :  
Description
The Standard Doclet produces incorrect method signatures when documenting a class that extends a package private super type. This
is a side effect of the fix for JDK-8157000. The logic for that enhancement should check if it is a simple override AND the super-type is documentable before flagging the methods in the sub-type as an overriding method.

The classes known to suffer from this issue as java.lang.StringBuffer and java.lang.StrinBuilder, the super-type is
java.lang.AbstractStringBuilder which is package private.
Comments
Deferral approved by component lead.
06-03-2018

ILW=>MMH=>P3 This bug should be deferred as it impacts only the JDK API documentation, specifically for two classes java.lang.StringBuffer and java.lang.StringBuilder, by exposing the return type to be a package private implementation class. This will have minimal impact to the customers who use the javadoc tool, as the new --override-methods=summary is an opt-in flag, and most users will not try this, even if they did this issue is a corner case, specific to the implementation of the above two classes.
01-03-2018