JDK-6875861 : javadoc build warning on java.util.Properites from unconventional @see ordering
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-08-26
  • Updated: 2010-04-02
  • Resolved: 2009-09-11
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 Other
7 b72Fixed OpenJDK6Fixed
Description
The javadoc for java.util.Properites has @see tags before the main specification of the class is done.  This causes an arguably spurious warning from javadoc.
Comments
SUGGESTED FIX # HG changeset patch # User darcy # Date 1251251906 25200 # Node ID 196c7bb551e76439da733e8a5f0b13a2f3c9c468 # Parent b115cf94685275f6961a4cafb5edc0595dd4c05f 6875861: javadoc build warning on java.util.Properites from unconventional @see ordering Reviewed-by: martin --- a/src/share/classes/java/util/Properties.java Tue Aug 25 15:14:53 2009 -0700 +++ b/src/share/classes/java/util/Properties.java Tue Aug 25 18:58:26 2009 -0700 @@ -101,11 +101,11 @@ import java.io.BufferedWriter; * &lt;!ATTLIST entry key CDATA #REQUIRED&gt; * </pre> * + * <p>This class is thread-safe: multiple threads can share a single + * <tt>Properties</tt> object without the need for external synchronization. + * * @see <a href="../../../technotes/tools/solaris/native2ascii.html">native2ascii tool for Solaris</a> * @see <a href="../../../technotes/tools/windows/native2ascii.html">native2ascii tool for Windows</a> - * - * <p>This class is thread-safe: multiple threads can share a single - * <tt>Properties</tt> object without the need for external synchronization. * * @author Arthur van Hoff * @author Michael McCloskey
26-08-2009
EVALUATION Removing warnings is good.
26-08-2009