JDK-4937327 : (spec) Many classes do not have javadoc tags for type parameters
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2003-10-14
  • Updated: 2017-07-20
  • Resolved: 2017-07-20
Related Reports
Relates :  
JDK-4881740 - retrofit collection classes to use generics
Relates :  
JDK-5017749 - (reflect spec) reflection classes may need additional API for generic signatures
Relates :  
JDK-4830575 - (spec) Docs for java.lang and java.lang.ref need to reflect generics
Description
The ability to document a type parameter was added to javadoc long after the libraries were first generified, so "early adopters" (collections framework, thread locals, weak refs) do not have javadoc tags for their type parameters.
Comments
I'm closing this issue as there hasn't been any comments since 2005. A lot has changed since this issue was created, not least is that the build will fail now if the javadoc for type parameters is missing.
20-07-2017
EVALUATION This looks like a more generic version of bug 4830575 which requested type parameters for all of java.lang and java.lang.ref. As a result the following bugs were open: 5003030 covers java.lang.ref 5017749 covers java.lang.reflect There may still be additional spec work to cover other portions of java.lang as indicated in this report.
20-10-2005
EVALUATION Doc no longer owns API spec changes. Am assigning this to engineering. Such tags may now already exist in the sources. Engineering would know which classes still need the tags, and could probably add them in as they are working on the code.
23-09-2005
EVALUATION Adding javadoc tags for type parameters to all classes would require a dedicated effort. At the present, docs does not have the resources to fix this bug. ###@###.### 2003-10-16
16-10-2003