JDK-4959985 : Javadoc BreakIterator warning is no longer current.
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2003-11-26
  • Updated: 2017-05-16
  • Resolved: 2003-12-19
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.
5.0 b32Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
In Merlin, a "javadoc -breakiterator" option was added.  For English
only, this forces the use of BreakIterator.  We also publicized our
intention to use BreakIterator exclusively in "the next major release".
When "-breakiterator" is not given and the two algorithms yield
different results, the following verbose warning is emitted by the tool:
    warning - The first sentence is interpreted to be:
    This sentence is different from what will be interpreted as the first
    sentence in the next major release (when that interpretation will be
    internationalized), which is:
    To avoid this note, change the doc comment to make this a proper first
    sentence, then use -breakiterator from that point forward, which will
    output this new sentence.

However, it was decided that changing the default English algorithm
was ill-advised for Tiger, and probably any other release.  So, the
warning message should go away.

Furthermore, in a future release (hopefully 1.5.1) we will add new
javadoc tags to allow one to mark summaries explicitly and avoid using
heuristics of any kind.  This is how it probably should have been from
the start.  Given this the warning message can actually be seen as
doing harm, since its advice on how to fix problem comments does not
align with our actual plans.

More background info can be found here:

    4890489: -breakiterator should be the default (possibly only) option
    4921374: Add tag to explicitly mark the end of the summary
    4959973: please warn when I don't use @summary

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b32 tiger-beta


EVALUATION The warning is no longer current or appropriate. It should be removed. Keep track of warnings currently produced by the J2SE build, so that we can fix our own doc comments at a future date. ###@###.### 2003-11-25