RFR: 8073713 javadoc warnings in serviceability code
Markus Gronlund
markus.gronlund at oracle.com
Tue Feb 24 09:12:34 UTC 2015
Looks good.
/Markus
-----Original Message-----
From: Staffan Larsen
Sent: den 24 februari 2015 10:08
To: serviceability-dev
Subject: RFR: 8073713 javadoc warnings in serviceability code
Please review these small fixes to javadoc in some of the serviceability code.
Thanks,
/Staffan
diff --git a/src/java.management/share/classes/com/sun/management/HotSpotDiagnosticMXBean.java b/src/java.management/share/classes/com/sun/management/HotSpotDiagnosticMXBean.java
--- a/src/java.management/share/classes/com/sun/management/HotSpotDiagnosticMXBean.java
+++ b/src/java.management/share/classes/com/sun/management/HotSpotDiagno
+++ sticMXBean.java
@@ -45,7 +45,7 @@
* All methods throw a {@code NullPointerException} if any input argument is
* {@code null} unless it's stated otherwise.
*
- * @see ManagementFactory#getPlatformMXBeans(Class)
+ * @see
+ java.lang.management.ManagementFactory#getPlatformMXBeans(Class)
*/
@jdk.Exported
public interface HotSpotDiagnosticMXBean extends PlatformManagedObject { diff --git a/src/jdk.attach/share/classes/com/sun/tools/attach/AttachOperationFailedException.java b/src/jdk.attach/share/classes/com/sun/tools/attach/AttachOperationFailedException.java
--- a/src/jdk.attach/share/classes/com/sun/tools/attach/AttachOperationFailedException.java
+++ b/src/jdk.attach/share/classes/com/sun/tools/attach/AttachOperationF
+++ ailedException.java
@@ -46,7 +46,7 @@
* Constructs an <code>AttachOperationFailedException</code> with
* the specified detail message.
*
- * @param s the detail message.
+ * @param message the detail message.
*/
public AttachOperationFailedException(String message) {
super(message);
diff --git a/src/jdk.jdi/share/classes/com/sun/jdi/InterfaceType.java b/src/jdk.jdi/share/classes/com/sun/jdi/InterfaceType.java
--- a/src/jdk.jdi/share/classes/com/sun/jdi/InterfaceType.java
+++ b/src/jdk.jdi/share/classes/com/sun/jdi/InterfaceType.java
@@ -145,7 +145,7 @@
* not be done from the client's event handler thread.
* <p>
* The resumption of other threads during the invocation can be prevented
- * by specifying the {@link #INVOKE_SINGLE_THREADED}
+ * by specifying the {@link ClassType#INVOKE_SINGLE_THREADED}
* bit flag in the <code>options</code> argument; however,
* there is no protection against or recovery from the deadlocks
* described above, so this option should be used with great caution.
More information about the serviceability-dev
mailing list