JDK-8220497 : Improve Javadoc search feature and add test coverage
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-03-12
  • Updated: 2020-04-22
  • Resolved: 2019-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 13
13 b19Fixed
Related Reports
Duplicate :  
JDK-8172227 - Javadoc Search does not support searching for members of classes with CamelCase input
Duplicate :  
JDK-8176051 - Javadoc search: camel case search doesn't work with indexes
Relates :  
JDK-8223252 - Update Javadoc help page with new search features
Relates :  
JDK-8178982 - Javadoc search specification
Sub Tasks
JDK-8223253 :  
Release Note: Improved Javadoc Search - Closed
Description
Working on JDK-8178982 we found a few shortcomings in the current search feature in Javadoc, and a came up with a few ways to improve it. These will be defined in  detail in a new spec produced as part of JDK-8178982. Here is a short summary of changes:

 - Match against word boundaries instead of anywhere in a name, e.g. `in` will match `invoke` but not `print`
 - Allow search to go all the way from package name to member name
 - Allow partial/camel case style matches anywhere, e.g. `j.l.Obj.e` will match `java.lang.Object.equals(Object)`
 - Try to provide better ranking of results and suppress peripheral matches
 - Implement and add tests to verify search works as intended by executing the actual browser search script