Bug 468491 - Need to update web readme.html/php for 4.5 (Mars)
initial rough draft with blind corrections to version number, etc.
diff --git a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
index 7c56996..d8b056f 100644
--- a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
+++ b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<style type="text/css">
table.platforms {
border-width: 1px;
@@ -29,13 +29,13 @@
background-color: #F4EEFF;
}
</style>
-<title>Eclipse Project Release Notes 4.4</title>
+<title>Eclipse Project Release Notes 4.5</title>
</head>
<body>
<h1>Eclipse Project Release Notes</h1>
-<p>Release 4.4.0<br/>
-Last revised June 5, 2014</p>
+<p>Release 4.5.0<br/>
+Last revised June 3, 2015</p>
<p 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>
@@ -61,7 +61,7 @@
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.4 release of the Eclipse Project is developed on a mix
+ In general, the 4.5 release of the Eclipse Project is developed on a mix
of Java SE 6 and Java SE 7 VMs. As such, the Eclipse SDK as a whole
is targeted at all modern, desktop Java VMs. Most functionality is available for
Java SE 6 level development everywhere, and extended development capabilities are made
@@ -76,7 +76,7 @@
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.4 is tested and validated on the following reference platforms
+<p>Eclipse 4.5 is tested and validated on the following reference platforms
(this list is updated over the course of the release cycle):</p>
<center>
@@ -249,57 +249,57 @@
<p>German and Japanese locales are tested.</p>
<h2>2. <a name="Compatibility"></a>Compatibility with Previous Releases</h2>
-<h3>Compatibility of Release 4.4 with 4.3</h3>
-<p>Eclipse 4.4 is compatible with Eclipse 4.3 (and all earlier 3.x versions).</p>
+<h3>Compatibility of Release 4.5 with 4.4</h3>
+<p>Eclipse 4.5 is compatible with Eclipse 4.4 (and all earlier 3.x versions).</p>
-<p><strong>API Contract Compatibility:</strong> Eclipse SDK 4.4 is upwards
- contract-compatible with Eclipse SDK 4.3 except in those areas noted in the
+<p><strong>API Contract Compatibility:</strong> Eclipse SDK 4.5 is upwards
+ contract-compatible with Eclipse SDK 4.4 except in those areas noted in the
<a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_4_porting_guide.html" target="_top">
- <em>Eclipse 4.4 Plug-in Migration Guide</em>
+ <em>Eclipse 4.5 Plug-in Migration Guide</em>
</a>. Programs that use affected APIs and extension points will need to be ported
- to Eclipse SDK 4.4 APIs. Downward contract compatibility
- is not supported. There is no guarantee that compliance with Eclipse SDK 4.4
- APIs would ensure compliance with Eclipse SDK 4.3 APIs. Refer to
+ to Eclipse SDK 4.5 APIs. Downward contract compatibility
+ is not supported. There is no guarantee that compliance with Eclipse SDK 4.5
+ APIs would ensure compliance with Eclipse SDK 4.4 APIs. Refer to
<a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
<em>Evolving Java-based APIs</em>
</a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
-<p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.4 is upwards
- binary-compatible with Eclipse SDK 4.3 except in those areas noted in the
+<p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.5 is upwards
+ binary-compatible with Eclipse SDK 4.4 except in those areas noted in the
<a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_4_porting_guide.html" target="_top">
- <em>Eclipse 4.4 Plug-in Migration Guide</em>
+ <em>Eclipse 4.5 Plug-in Migration Guide</em>
</a>. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK
- 4.4 will not be usable in Eclipse SDK 4.3. Refer to
+ 4.5 will not be usable in Eclipse SDK 4.4. Refer to
<a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
<em>Evolving Java-based APIs</em>
</a> for a discussion of the kinds of API changes that maintain binary compatibility.</p>
-<p><strong>Source Compatibility:</strong> Eclipse SDK 4.4 is upwards source-compatible
- with Eclipse SDK 4.3 except in the areas noted in the
+<p><strong>Source Compatibility:</strong> Eclipse SDK 4.5 is upwards source-compatible
+ with Eclipse SDK 4.4 except in the areas noted in the
<a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_4_porting_guide.html" target="_top">
- <em>Eclipse 4.4 Plug-in Migration Guide</em>
+ <em>Eclipse 4.5 Plug-in Migration Guide</em>
</a>. This means that source files written
- to use Eclipse SDK 4.3 APIs might successfully compile and run against Eclipse
- SDK 4.4 APIs, although this is not guaranteed. Downward source compatibility
+ to use Eclipse SDK 4.4 APIs might successfully compile and run against Eclipse
+ SDK 4.5 APIs, although this is not guaranteed. Downward source compatibility
is not supported. If source files use new Eclipse SDK APIs, they will not be
usable with an earlier version of the Eclipse SDK. </p>
-<p><strong>Workspace Compatibility:</strong> Eclipse SDK 4.4 is upwards
+<p><strong>Workspace Compatibility:</strong> Eclipse SDK 4.5 is upwards
workspace-compatible with earlier 3.x and 4.x versions of the Eclipse SDK unless noted.
- This means that workspaces and projects created with Eclipse SDK 4.3, 4.2, .. 3.0 can be successfully
- opened by Eclipse SDK 4.4 and upgraded to a 4.4 workspace. This includes both
+ This means that workspaces and projects created with Eclipse SDK 4.4, 4.3, 4.2, .. 3.0 can be successfully
+ opened by Eclipse SDK 4.5 and upgraded to a 4.5 workspace. This includes both
hidden metadata, which is localized to a particular workspace, as well as metadata
files found within a workspace project (e.g., the .project file), which may
propagate between workspaces via file copying or team repositories. Individual
- plug-ins developed for Eclipse SDK 4.4 should provide similar upwards compatibility
+ plug-ins developed for Eclipse SDK 4.5 should provide similar upwards compatibility
for their hidden and visible workspace metadata created by earlier versions;
- 4.4 plug-in developers are responsible for ensuring that their plug-ins recognize
+ 4.5 plug-in developers are responsible for ensuring that their plug-ins recognize
metadata from earlier versions and process it appropriately. User
interface session state may be discarded when a workspace is upgraded. Downward
workspace compatibility is not supported. A workspace created (or opened) by
- a product based on Eclipse 4.4 will be unusable with a product based on an earlier
+ a product based on Eclipse 4.5 will be unusable with a product based on an earlier
version of Eclipse. Visible metadata files created (or overwritten) by Eclipse
- 4.4 will generally be unusable with earlier versions of Eclipse. </p>
+ 4.5 will generally be unusable with earlier versions of Eclipse. </p>
<p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes,
and certainly everything in a package with "internal" in its name or
@@ -347,7 +347,7 @@
<h4>Installation/Configuration issues that can cause Eclipse to fail start</h4>
<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.4 requires
+ <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 4.5 requires
at least a Java SE 6. Perhaps an older version of the VM is being found in
your path. To explicitly specify which VM to run with, use the Eclipse <tt>-vm</tt>
command-line argument. (See also the <a href="#RunningEclipse">Running Eclipse</a>
@@ -364,7 +364,7 @@
<li>Eclipse must be installed to a clean directory and not installed over top of
a previous installation. If you have done this then please re-install to a new
directory. If your workspace is in a child directory of your old installation
-directory, then see the instructions below on "<a href="#upgrading">Upgrading Workspace from a
+directory, then see the instructions below on "<a href="#Upgrading">Upgrading Workspace from a
Previous Release"</a>.</li>
<li>Java sometimes has difficulty detecting whether a file system is writable. In
@@ -432,10 +432,10 @@
It is imperative that 64-bit builds are downloaded and used if a 64-bit Java
runtime environment has been installed. Below are two sample tarball names of
-version 4.4 of the Eclipse SDK packaged for 32-bit and 64-bit processors.
+version 4.5 of the Eclipse SDK packaged for 32-bit and 64-bit processors.
-<pre>eclipse-SDK-4.4-linux-gtk.tar.gz (32-bit)
-eclipse-SDK-4.4-linux-gtk-x86_64.tar.gz (64-bit)</pre>
+<pre>eclipse-SDK-4.5-linux-gtk.tar.gz (32-bit)
+eclipse-SDK-4.5-linux-gtk-x86_64.tar.gz (64-bit)</pre>
<p>To run Eclipse with an alternate Java runtime environment, the path to the Java
virtual machine's binary must be identified. With an Eclipse installation from
@@ -1229,7 +1229,7 @@
</p>
<h4>Missing @since tag API Tools problems on interface fields containing @noreference tag</h4>
-<p>The Eclipse platform 4.4 release will not allow the API Tools @noreference tag on interface fields. This was
+<p>The Eclipse platform 4.5 release will not allow the API Tools @noreference tag on interface fields. This was
changed because all interface fields are constant fields that cannot support the @noreference restriction. The
tag was allowed in previous releases and this usage will now be considered an API change requiring a @since tag.
It is recommended that you create an API Tools filter for the missing @since tag problem. This filter can be
@@ -1242,7 +1242,7 @@
by running the Eclipse executable included with the release (you also need a Java SE 6
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.4-win32</code>, the executable is <code>c:\eclipse-SDK-4.4-win32\eclipse\eclipse.exe</code>.
+installed at <code>c:\eclipse-SDK-4.5-win32</code>, the executable is <code>c:\eclipse-SDK-4.5-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>
@@ -1342,7 +1342,7 @@
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>
-<h2 id="upgrading">5. Upgrading Workspace from a Previous Release</h2>
+<h2 name="Upgrading">5. Upgrading Workspace from a Previous Release</h2>
<h3>Users who don't use "-data"</h3>
<p>If you weren't previously using "-data" to specify your workspace,
@@ -1407,8 +1407,8 @@
<h2>6. <a name="InteroperabilityWithPreviousReleases">Interoperability with
Previous Releases</a></h2>
-<h3>6.1 Interoperability of Release 4.4 with previous releases</h3>
-<h4>Sharing projects between heterogeneous Eclipse 4.4 and 4.3</h4>
+<h3>6.1 Interoperability of Release 4.5 with previous releases</h3>
+<h4>Sharing projects between heterogeneous Eclipse 4.5 and 4.4</h4>
<p>Special care is required when a project in a team repository is being loaded
and operated on by developers using Eclipse-based products based on different
feature or plug-in versions. The general problem is that the existence,
@@ -1416,61 +1416,61 @@
to a particular feature or plug-in version, and differ between versions. The
workspace compatibility guarantees only cover cases where all developers upgrade
their Eclipse workspaces in lock step. In those cases there should be no problem
-with shared metadata. However, when some developers are working in Eclipse 4.4
+with shared metadata. However, when some developers are working in Eclipse 4.5
while others are working in Eclipse 3.x, there are no such guarantees.
This section provides advice for what to do and not to do. It addresses the
specific issues with the Eclipse SDK.</p>
-<p>The typical failure mode is noticed by the 4.4 user. 4.4 metadata is lost
-when a 4.3 user saves changes and then commits the updated metadata files to the
+<p>The typical failure mode is noticed by the 4.5 user. 4.5 metadata is lost
+when a 4.4 user saves changes and then commits the updated metadata files to the
repository. Here's how things typically go awry:</p>
<ul>
- <li>A user working in Eclipse 4.4 creates or modifies a project in a way that
- results in changes to a shared metadata file that rely on 4.4-specific
+ <li>A user working in Eclipse 4.5 creates or modifies a project in a way that
+ results in changes to a shared metadata file that rely on 4.5-specific
information. The user then commits the updated project files, including the
shared metadata file, to the shared repository.</li>
- <li>Another user working in Eclipse 4.3 or earlier shares this project from the same
- repository. The 4.4-specific information in the shared metadata file is not
- understood by Eclipse 4.3, and is generally discarded or ignored without
+ <li>Another user working in Eclipse 4.4 or earlier shares this project from the same
+ repository. The 4.5-specific information in the shared metadata file is not
+ understood by Eclipse 4.4, and is generally discarded or ignored without
warning. The user modifies the project in a way that results in changes to
the shared metadata file, causing the shared metadata file to be rewritten
- without any of the 4.4-specific information. The user commits the updated
+ without any of the 4.5-specific information. The user commits the updated
project files, including the shared metadata file, to the shared repository.
The user is generally unaware that shared information has just been lost as
a result of their actions.</li>
- <li>A user working in Eclipse 4.4 picks up the changes to a project from the
+ <li>A user working in Eclipse 4.5 picks up the changes to a project from the
shared repository, including the updated shared metadata file. The user may
be unaware that they have just taken a retrograde step until later when
things start to malfunction.</li>
</ul>
<p>Here are some things to watch out for when sharing projects between
-Eclipse 4.4 and earlier releases:</p>
+Eclipse 4.5 and earlier releases:</p>
<ul>
<li><b>Virtual folders</b> -
- Eclipse 4.4 supports a notion of <i>virtual folders</i> that did not exist
- in Eclipse 3.5 or earlier. If such virtual folders are created in 4.4, and the project
+ Eclipse 4.5 supports a notion of <i>virtual folders</i> that did not exist
+ in Eclipse 3.5 or earlier. If such virtual folders are created in 4.5, and the project
is subsequently loaded into an Eclipse 3.5 or earlier workspace, these folders
will not be recognized. Recommendation: avoid creating virtual folders where project
compatibility with Eclipse 3.5 or earlier is required.</li>
<li><b>Resource filters</b> -
- Eclipse 4.4 supports a notion of <i>resource filters</i> that did not exist
- in Eclipse 3.5 or earlier. If such filters are added to resources in 4.4, and the project
+ Eclipse 4.5 supports a notion of <i>resource filters</i> that did not exist
+ in Eclipse 3.5 or earlier. If such filters are added to resources in 4.5, and the project
is subsequently loaded into an Eclipse 3.5 or earlier workspace, these filters
will not be recognized. Recommendation: avoid creating resource filters where project
compatibility with Eclipse 3.5 or earlier is required.</li>
<li><b>Predefined path variables</b> -
- Eclipse 4.4 supports a set of built in path variables that can be used as the basis
+ Eclipse 4.5 supports a set of built in path variables that can be used as the basis
for linked resource locations. Such variables will not be defined automatically in
Eclipse 3.5 or earlier. If compatibility with 3.5 or earlier workspace is required,
users on 3.5 or earlier workspaces will need to define such path variables manually.
</li>
</ul>
-<h4>Using Eclipse 4.4 to develop plug-ins that work in Eclipse 4.3</h4>
-<p>It is also possible (and reasonable) to use Eclipse 4.4 to develop a plug-in
- intended to work in Eclipse 4.3 or earlier. Use the <b>Plug-in Development >
+<h4>Using Eclipse 4.5 to develop plug-ins that work in Eclipse 4.4</h4>
+<p>It is also possible (and reasonable) to use Eclipse 4.5 to develop a plug-in
+ intended to work in Eclipse 4.4 or earlier. Use the <b>Plug-in Development >
Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse
- 4.3 install. This ensures that the code for your plug-in is being compiled and
- tested against Eclipse 4.3 APIs, extension points, and plug-ins. (The above
+ 4.4 install. This ensures that the code for your plug-in is being compiled and
+ tested against Eclipse 4.4 APIs, extension points, and plug-ins. (The above
list of concerns do not apply since they affect the layout and interpretation
of files in the plug-in <i>project</i> but none affect the actual deployed form
of the plug-in.)</p>
@@ -1490,9 +1490,9 @@
<h2><a name="appendix">Appendix 1: Execution Environment by Bundle</a></h2>
-<p>In the table below, the "4.4 minimum execution environment"
+<p>In the table below, the "4.5 minimum execution environment"
column indicates the minimum Java class library requirements of each bundle
- for the 4.4 release, where the value is one of:</p>
+ for the 4.5 release, where the value is one of:</p>
<table border="0" width="90%">
<tbody>
<tr>
@@ -1555,14 +1555,14 @@
</table>
<p><b>Table of minimum execution environments by bundle.</b> (See also the
- <a href="https://projects.eclipse.org/projects/rt.equinox/releases/4.4.0/plan">Equinox Project plan</a>
+ <a href="https://projects.eclipse.org/projects/rt.equinox/releases/4.5.0/plan">Equinox Project plan</a>
for the execution environment requirements of bundles contributed via that project.)</p>
<table border="1">
<tbody>
<tr>
<td width="290"><strong>Bundle</strong></td>
- <td width="60"><div align="center"><p align="center"><b>4.4<br/>minimum<br/>execution<br/>environment</b></p></div></td>
+ <td width="60"><div align="center"><p align="center"><b>4.5<br/>minimum<br/>execution<br/>environment</b></p></div></td>
</tr>
<tr>
<td>com.ibm.icu</td>
