changeset 57497:66627a94e828

8229847: AttachProvider javadoc page needs an update Summary: Replace Sun references with Oracle references in AttachProvider javadoc Reviewed-by: amenkov, dholmes
author sspitsyn
date Fri, 10 Jan 2020 01:36:48 +0000
parents 5de55aa0cfdb
children 3e80284479b0
files src/jdk.attach/share/classes/com/sun/tools/attach/spi/AttachProvider.java
diffstat 1 files changed, 5 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/src/jdk.attach/share/classes/com/sun/tools/attach/spi/AttachProvider.java	Thu Jan 09 08:31:41 2020 -0800
+++ b/src/jdk.attach/share/classes/com/sun/tools/attach/spi/AttachProvider.java	Fri Jan 10 01:36:48 2020 +0000
@@ -46,17 +46,18 @@
  * <p> An attach provider implementation is typically tied to a Java virtual
  * machine implementation, version, or even mode of operation. That is, a specific
  * provider implementation will typically only be capable of attaching to
- * a specific Java virtual machine implementation or version. For example, Sun's
+ * a specific Java virtual machine implementation or version. For example, Oracle's
  * JDK implementation ships with provider implementations that can only attach to
- * Sun's <i>HotSpot</i> virtual machine. In general, if an environment
+ * Oracle's <i>HotSpot</i> virtual machine. In general, if an environment
  * consists of Java virtual machines of different versions and from different
  * vendors then there will be an attach provider implementation for each
  * <i>family</i> of implementations or versions.
  *
  * <p> An attach provider is identified by its {@link #name <i>name</i>} and
  * {@link #type <i>type</i>}. The <i>name</i> is typically, but not required to
- * be, a name that corresponds to the VM vendor. The Sun JDK implementation,
- * for example, ships with attach providers that use the name <i>"sun"</i>. The
+ * be, a name that corresponds to the VM vendor. The Oracle JDK implementation,
+ * for example, ships with attach providers that use the package name <i>"sun"</i>
+ * (for historical reasons). The
  * <i>type</i> typically corresponds to the attach mechanism. For example, an
  * implementation that uses the Doors inter-process communication mechanism
  * might use the type <i>"doors"</i>. The purpose of the name and type is to