blob: b8aa38f0c33d3dfccf2d34534ef3b8e0698cee62 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<title>Upgrading from 3.1 to 3.1.1 using update manager</title>
<link rel="stylesheet" href="" type="text/css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<h3>Upgrading from 3.1 to 3.1.x using update manager</h3>
<p>To upgrade from 3.1 to 3.1.x using update manager, you must manually specify
a new update site.<a href="#footnote1"><sup>1</sup></a> These instructions describe
how to update from 3.1 to 3.1.x or from 3.1.1 to 3.1.2 only. These instructions
should <u>not</u> be used to upgrade from a 3.0.x build to 3.1 or 3.1.1. </p>
<p>In Eclipse 3.1, select</p>
<p><strong>Help</strong> --&gt; <strong>Software Updates</strong> --&gt; <strong>Find and Install</strong> --&gt; <strong>Search for New features to Install</strong> </p>
<p><img src="images/featureupdates.JPG" width="576" height="515"> </p>
<p>Select <strong>New Remote Site</strong>.</p>
<p><img src="images/tovisit.JPG" width="576" height="516"></p>
<p> In the <strong>New Update Site</strong> dialog, enter Name: <strong>Eclipse
SDK 3.1.x Updates</strong> and URL: <strong></strong></strong>
<p><strong></strong><img src="images/newsite.JPG" width="356" height="154"></p>
<p>&nbsp; </p>
<p>Select <strong>OK</strong>.</p>
<p><img src="images/check.JPG" width="600" height="538"></p>
<p>Ensure that only <strong>Eclipse 3.1.x SDK updates</strong> check box is selected
and press <strong>Finish</strong>.</p>
<p>A list of mirrors will appear that have the 3.1.x updates. Select a mirror
that is geographically suitable for you and select OK </p>
<p><img src="images/mirrors.JPG" width="456" height="377"></p>
<p>The update process should now proceed as usual.</p>
<p><a name="footnote1"><sup>1</sup> The eclipse update site is specified as
in Eclipse 3.1 features. However, you cannot upgrade to 3.0 to 3.1 using update
manager because the startup.jar and eclipse executable were upgraded from 3.0
to 3.1 and update manager does not currently support upgrading these files.
If we placed the 3.1.x updates in the standard 3.x update site, this could cause
problems for 3.0 installations. Consquently, we have created a new update site
for the 3.1.x maintenance streams See for further details.</p>