Fixed bug 422682: Running Eclipse section incorrectly states Java SE 5 JRE as requirement
diff --git a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm b/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
index 28fcfc2..75432f7 100644
--- a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
+++ b/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2011. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
@@ -15,10 +15,9 @@
<h1>Running Eclipse</h1>
<!-- ************* BEGIN SECTION COPIED FROM README FILE **************** -->
<p>After installing the Eclipse SDK in a directory, you can start the Workbench
-by running the Eclipse executable included with the release (you also need a Java SE 5
-JRE, not included with the Eclipse SDK). On Windows, the executable file is called <samp>eclipse.exe</samp>,
+by running the Eclipse executable included with the release (you also need at least a JDK6 or JRE 6, not included with the Eclipse SDK). On Windows, the executable file is called <samp>eclipse.exe</samp>,
and is located in the <code>eclipse</code> sub-directory of the install. If
-installed at <code>c:\eclipse-SDK-4.1-win32</code>, the executable is <code>c:\eclipse-SDK-4.1-win32\eclipse\eclipse.exe</code>.
+installed at <code>c:\eclipse-SDK-4.4-win32</code>, the executable is <code>c:\eclipse-SDK-4.4-win32\eclipse\eclipse.exe</code>.
<b>Note:</b> Set-up on most other operating environments is analogous. Special
instructions for Mac OS X are listed <a href="#macosx">below</a>.</p>
@@ -38,11 +37,10 @@
"384M" (384 megabytes -- the default).
</p>
<p>
-When using an Oracle (Sun) VM, you may also need to increase the size of the permanent
+When using an Oracle JRE, you may also need to increase the size of the permanent
generation memory. The default maximum is 64 megabytes, but more may
be needed depending on your plug-in configuration and use. When the VM runs
out of permanent generation memory, it may crash or hang during class loading.
-This failure is less common when using Sun JRE version 1.5.0_07 or greater.
The maximum permanent generation size is increased using the -XX:MaxPermSize=<memory size> argument:</p>
<blockquote>
<p><code>eclipse -vmargs -XX:MaxPermSize=<memory size></code></p>
@@ -69,7 +67,7 @@
<p>Here is a typical Eclipse command line: </p>
<blockquote>
- <p><code>eclipse -vm c:\jdk5u22\jre\bin\javaw</code></p>
+ <p><code>eclipse -vm c:\jdk7u45\jre\bin\javaw</code></p>
</blockquote>
<p><i>Tip:</i> It's generally a good idea to explicitly specify which Java VM to
use when running Eclipse. This is achieved with the "<code>-vm</code>"
