JDK-8137067 : Deprecate the old doclet
  • Type: Bug
  • Component: docs
  • Sub-Component: doclet
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2015-09-23
  • Updated: 2016-06-01
  • Resolved: 2016-06-01
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.
Related Reports
Duplicate :  
Relates :  
Relates :  
Once the new Doclet API has been integrated, deprecate the old doclet and taglet by adding @Deprecated annotation on the top level classes, and add the @deprecated javadoc tag in the API doc, giving the reader info about the replacement, including pointing to the new implementation's API docs.
See JDK-8157606

How about making the javadoc tool print out a suitable scary warning if (but only if) the old doclet API is being used. Anyone using the standard doclet, or other instances of the new doclet API, would not get the warning.

You do not have to wait to for the new doclet API to be integrated; you could prepare the changeset, reviews and CCC for this while completing the new Doclet API work, and then push the two together.