--- old/application/org.openjdk.jmc.updatesite.ide/src/main/resources/run-on-jdk-instructions/index.html 2019-01-08 22:12:56.947174999 +0530 +++ new/application/org.openjdk.jmc.updatesite.ide/src/main/resources/run-on-jdk-instructions/index.html 2019-01-08 22:12:56.847125000 +0530 @@ -1,10 +1,10 @@
-
- + |
To fully take advantage of running Mission Control in your Eclipse IDE, you need to run Eclipse on a JDK installation.
+
To fully take advantage of running JDK Mission Control in your Eclipse IDE, you need to run Eclipse on a JDK installation.
Attaching to locally running JVMs will only work if you're running with a JDK.
Follow the instructions below to run on a HotSpot JDK.
The easiest way to change the JVM on which to start Eclipse is by modifying the eclipse.ini file. You can also set the -vm on the command line used to start Eclipse. In windows you would typically do that in the shortcut you use to launch Eclipse. Here is an example ini file:
-showsplash
org.eclipse.platform
-vm
D:/java/jdk7_40/jre/bin/
You can also configure JVM options by using -vmargs on commandline or eclipse.ini:
-
-showsplash
org.eclipse.platform
-vm
D:/java/jdk8_131/jre/bin/
-vmargs
<JVM options on separate lines>
If you use JDK 9 (or later) to run Eclipse, the following JVM options are needed for Mission Control to work properly:
+If you use JDK 9 (or later) to run Eclipse, the following JVM options are needed for JDK Mission Control to work properly:
-Djdk.attach.allowAttachSelf=true
--add-exports=java.xml/com.sun.org.apache.xerces.internal.parsers=ALL-UNNAMED
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED