Bug 493368 - readme - updated content in rcp feature root
Change-Id: If23375734542b7babb1a29593f25b1accb5c6e24
diff --git a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
index 92025ef..0479447 100644
--- a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
+++ b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
@@ -8,7 +8,7 @@
<h1>Eclipse Project Release Notes</h1>
<p>Release 4.6.0 (Neon)<br/>
-Last revised May 10, 2016</p>
+Last revised May 22, 2016</p>
<p style="text-align:left;"><strong>This software is OSI Certified Open Source Software.<br/>
OSI Certified is a certification mark of the Open Source Initiative. </strong></p>
@@ -37,11 +37,8 @@
environments, requiring their source code to only reference facilities available
in particular class libraries (e.g. J2ME Foundation 1.1, J2SE 1.4, Java 5, etc).</p>
<p>
- In general, the 4.6 release of the Eclipse Project is developed on a mix
- of Java SE 7 and Java SE 8 VMs. As such, the Eclipse SDK as a whole
- is targeted at all modern, desktop Java VMs. Most functionality is available for
- Java SE 7 level development everywhere, and extended development capabilities are made
- available on the VMs that support them.</p>
+ In general, the 4.6 release of the Eclipse Project is developed on Java SE 8 VMs. As such, the Eclipse SDK as a whole
+ is targeted at all modern, desktop Java VMs.</p>
<p><a href="#appendix">Appendix 1</a> contains a table that indicates the class
library level required for each bundle.</p>
<p>There are many different implementations of the Java Platform running atop
@@ -52,207 +49,9 @@
them we cannot vouch for them. Problems encountered when running Eclipse on a
non-reference platform that cannot be recreated on any reference platform will
be given lower priority than problems with running Eclipse on a reference platform.</p>
-<p>Eclipse 4.6 is tested and validated on the following reference platforms
- (this list is updated over the course of the release cycle):</p>
+<p>Eclipse 4.6 is tested and validated on a number of reference platforms. For the
+complete list, see <a href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#target_environments">Target Environments in the 4.6 Plan</a>.</p>
-<div>
-<!-- NOTE: we intentionally do not want <style> in <head> because then if we
- wrap this HTML with a Solstice PHP theme, Solstice will ignore (or, replace)
- any <style> that is in <head>. Thus, this allows us to use our own style for
- table, with both plain HTML5 and Solstice wrapped PHP/HTML5. The 'scoped' attribute
- means to apply this style only to things 'in' the container parent (the <div>)
- and not whole document, and it is required for any <style> element not in <head>. -->
-<style type="text/css" scoped>
- table.platforms {
- margin: 0 auto;
- border-width: 1px;
- border-spacing: 0px;
- border-style: solid;
- border-collapse: separate;
- }
- table.platforms th {
- border-width: 1px;
- padding: 3px;
- border-style: inset;
- border-color: black;
- background-color: #B9A9FF;
- }
- table.platforms td {
- border-width: 1px 1px 1px 1px;
- padding: 3px 3px 3px 3px;
- border-style: inset inset inset inset;
- border-color: gray gray gray gray;
- }
- table.platforms tr.c0 td {
- background-color: #FDFDFD;
- }
- table.platforms tr.c1 td {
- background-color: #F4EEFF;
- }
-</style>
- <table class="platforms">
- <tr>
- <th>Operating System</th>
- <th>Version</th>
- <th>Hardware</th>
- <th>JRE</th>
- <th>Windowing System</th>
- </tr>
- <!-- ************ WINDOWS ************** -->
- <tr class="c0">
- <td rowspan="2">Windows</td>
- <td rowspan="2">7<br/>
- 8
- </td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 8u45<br/>
- Oracle Java 7u80<br/>
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- <td rowspan="2">Win32</td>
- </tr>
- <tr>
- <td rowspan="1">x86 64-bit</td>
- </tr>
- <!-- ************ RHEL ************** -->
- <tr class="c1">
- <td rowspan="5">Red Hat Enterprise Linux</td>
- <td rowspan="4">6</td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 8u45<br/>
- Oracle Java 7u80<br/>
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1<br/>
- Open JDK 7u40
- </td>
- <td rowspan="4">GTK+ 2</td>
- </tr>
- <tr class="c1">
- <td rowspan="1">x86 64-bit</td>
- </tr>
- <tr class="c1">
- <td rowspan="1">Power 32-bit</td>
- <td rowspan="2">
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- </tr>
- <tr class="c1">
- <td rowspan="1">Power 64-bit</td>
- </tr>
- <tr class="c1">
- <td rowspan="1">7</td>
- <td rowspan="1">x86 64-bit</td>
- <td rowspan="1">Open JDK 7u40</td>
- <td rowspan="1">GTK+ 3</td>
- </tr>
- <!-- ************ SLES ************** -->
- <tr class="c0">
- <td rowspan="4">SUSE Linux Enterprise Server</td>
- <td rowspan="4">11 SP2</td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 8u45<br/>
- Oracle Java 7u80<br/>
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- <td rowspan="4">GTK+ 2</td>
- </tr>
- <tr class="c0">
- <td rowspan="1">x86 64-bit</td>
- </tr>
- <tr class="c0">
- <td rowspan="1">Power 32-bit</td>
- <td rowspan="2">
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- </tr>
- <tr class="c0">
- <td rowspan="1">Power 64-bit</td>
- </tr>
- <!-- ************ Ubuntu ************** -->
- <tr class="c1">
- <td rowspan="4">Ubuntu Long Term Support</td>
- <td rowspan="2">12.04</td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 8u45<br/>
- Oracle Java 7u80<br/>
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
-
- </td>
- <td rowspan="2">GTK+ 3</td>
- </tr>
- <tr class="c1">
- <td rowspan="1">x86 64-bit</td>
- </tr>
- <tr class="c1">
- <td rowspan="2">14.04</td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 8u45<br/>
- Oracle Java 7u80<br/>
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- <td rowspan="2">GTK+ 3</td>
- </tr>
- <tr class="c1">
- <td rowspan="1">x86 64-bit</td>
- </tr>
- <!-- ************ Solaris ************** -->
- <tr class="c0">
- <td rowspan="2">Oracle Solaris</td>
- <td rowspan="2">10</td>
- <td rowspan="1">x86 32-bit</td>
- <td rowspan="2">
- Oracle Java 7u80</td>
- <td rowspan="2">GTK+ 2</td>
- </tr>
- <tr class="c0">
- <td rowspan="1">SPARC 32-bit</td>
- </tr>
- <!-- ************ HPUX ************** -->
- <tr class="c1">
- <td rowspan="1">HP-UX</td>
- <td rowspan="1">11i v3</td>
- <td rowspan="1">ia64 64-bit</td>
- <td rowspan="1">HP-UX Java 7u65</td>
- <td rowspan="1">GTK+ 2</td>
- </tr>
- <!-- ************ AIX ************** -->
- <tr class="c0">
- <td rowspan="2">IBM AIX</td>
- <td rowspan="2">7.1</td>
- <td rowspan="1">Power 32-bit</td>
- <td rowspan="2">
- IBM Java 7 SR9<br/>
- IBM Java 8 SR1
- </td>
- <td rowspan="2">GTK+ 2</td>
- </tr>
- <tr class="c0">
- <td rowspan="1">Power 64-bit</td>
- </tr>
-
- <!-- ************ Mac ************** -->
- <tr class="c1">
- <td rowspan="1">Apple Mac OS X</td>
- <td rowspan="1">10.10</td>
- <td rowspan="1">x86 64-bit</td>
- <td rowspan="1">
- Oracle Java 8u45<br/>
- Oracle Java 7u80</td>
- <td rowspan="1">Cocoa</td>
- </tr>
- </table>
-</div>
<p>As stated above, <i>we expect that Eclipse works fine on other current
Java VM and OS versions but we cannot flag these as reference platforms without
significant community support for testing them.</i></p>
@@ -366,7 +165,7 @@
<p>Here are some common problems that can cause Eclipse not to start:</p>
<ul>
<li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 4.6 requires
- at least a Java SE 7. Perhaps an older version of the VM is being found in
+ at least a Java SE 8. Perhaps an older version of the VM is being found in
your path. To explicitly specify which VM to run with, use the Eclipse <code>-vm</code>
command-line argument. (See also the <a href="#RunningEclipse">Running Eclipse</a>
section below.)</li>
@@ -464,7 +263,6 @@
is shown below:</p>
<code>searching for compatible vm...<br/>
- testing /usr/lib/jvm/java-7-icedtea...not found<br/>
testing /usr/lib/jvm/java-gcj...found</code>
<p>Once the path to the virtual machine's binary has been identified, try running
@@ -485,8 +283,6 @@
<code>-showsplash<br/>
org.eclipse.platform<br/>
---launcher.XXMaxPermSize<br/>
-256m<br/>
-vm<br/>
/opt/sun-jdk-1.6.0.02/bin/java<br/>
-vmargs<br/>
@@ -532,8 +328,6 @@
plugins/org.eclipse.equinox.launcher_1.0.200.v20090429-1630.jar<br/>
-showsplash<br/>
org.eclipse.platform<br/>
---launcher.XXMaxPermSize<br/>
-256m<br/>
-vmargs<br/>
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith<br/>
-Xms40m<br/>
@@ -785,10 +579,8 @@
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=183003">183003</a>)
</p>
Allocating enough memory and solving OutOfMemoryError
-<h4>Launching an inner eclipse can lead to PermGen errors</h4>
<p>
-On some Oracle JVMs, launching an inner eclipse during plug-in development can lead to PermGen errors
-for the inner eclipse. The native launcher checks the JVM and can add <i>-XX:MaxPermSize=256m</i>,
+The native launcher checks the JVM
but PDE launches simply use java and don't go through the native launchers. The workaround is to add
the appropriate JVM arg to your launch config or to the <i>Preferences > Java > Installed JREs</i>.
(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=339763">339763</a>)
@@ -1227,7 +1019,7 @@
<h2 id="RunningEclipse">4. Running Eclipse</h2>
<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 7
+by running the Eclipse executable included with the release (you also need a Java SE 8
JRE, 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.6-win32</code>, the executable is <code>c:\eclipse-SDK-4.6-win32\eclipse\eclipse.exe</code>.
@@ -1251,21 +1043,9 @@
<p>with the <code><memory size></code> value set to greater than
"1024M" (1024 megabytes -- the default).
</p>
+
<p>
-When using an Oracle VM below 1.8, 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 Oracle 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>
-</blockquote>
-<p>This argument may not be available for all VM versions and platforms; consult your VM documentation
-for more details.
-</p>
-<p>
-Note that setting memory sizes to be larger than the amount of available physical
+Note that setting memory sizes to be near or larger than the amount of available physical
memory on your machine will cause Java to "thrash" as it copies objects
back and forth to virtual memory, which will severely degrade your performance.
</p>
@@ -1332,6 +1112,40 @@
option from an account that has a write access to the install directory.
See <a href=" http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html">shared installs</a> in Eclipse
Help for more information.</p>
+<h3 id="SpecialOSRequirements">Special Operating System Requirements</h3>
+<h4 id="SpecialOSRequirementsAIX">AIX</h4>
+<p>In order for this version of Eclipse to run, GTK2 libraries and their dependencies
+must be installed and available on the library path (i.e. LIBPATH). These libraries
+are available from http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/alpha.html .
+To determine the full set of libraries required for installation, download and install the
+"gtk2" rpm, at which time any missing dependencies will be listed. These dependencies should
+be available for download from the same site.
+</p>
+<p>You can run Eclipse using the VM from IBM Developer Kit for AIX versions
+5 and 6. The IBM Developer Kit for AIX can be downloaded from:
+https://www.ibm.com/developerworks/java/jdk/aix/service.html
+</p>
+<h4 id="SpecialOSRequirementsHPUX">HPUX</h4>
+<p>In order for this version of Eclipse to run, GTK2 libraries must be installed
+and available on the library path (i.e. LD_LIBRARY_PATH).</p>
+
+<p>For example, export LD_LIBRARY_PATH=/opt/gtk_64bit/lib/hpux64/</p>
+
+<p>To prevent errors with workspace locking, the following command line should be
+used to launch Eclipse:</p>
+
+<p>"eclipse -vmargs -Dosgi.locking=none"</p>
+
+<p>Otherwise, eclipse may fail to create a lock file with reason: "Workspace in use or cannot be created, choose a different one."</p>
+
+<p>Note you might also need to add the -d64 option to the vmargs when using an Oracle JRE. (-vmargs -d64)</p>
+<h4 id="SpecialOSRequirementsSolaris">Solaris</h4>
+<p>This version of Eclipse works best with the latest version of GTK+ 2, but the earliest
+version supported is GTK+ 2.10.</p>
+
+<p>The GTK libraries must be available on the library path (i.e. LD_LIBRARY_PATH).</p>
+
+
<h2 id="Upgrading">5. Upgrading Workspace from a Previous Release</h2>
<h3>Users who don't use "-data"</h3>
