JDK-6964914 : javadoc does not output number of warnings using user written doclet
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-06-29
  • Updated: 2016-02-23
  • Resolved: 2011-04-20
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 7
7 b134Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Using a user written doclet, 19 warnings were generated but no text stating "19 warnings".
Compile attached doclet.
run as

javadoc -package -doclet Field_Test3 \jdk170\src\java\lang\Thread.java

There are 4 warning. on previous builds it would print
"4 warnings"
at completion. 
This may be a side effect of the -Xmaxerrs/maxwarns implementation.

Comments
EVALUATION Yes, this is a side effect of the -Xmaxerrs/-Xmaxwarns work. As a side effect of that work, TWO Messager objects are created, an initial one to handle errors during option decoding, and a later one to handle errors from processing source code. Messager is responsible for printing the final counts (NOT JavaCompiler.compile2). In the case where no counts are output, the wrong messager is being used.
04-10-2010

EVALUATION b99 is OK, b100 is not.
04-10-2010

EVALUATION Fault reproduced. As an aside, it's easy to generate standalone API that creates warnings by using Sun propertietary API and getting that warning.
04-10-2010