platform-update-home/doc/Test Scenarios/eclipse update.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.8, Mon Jun 3 01:23:04 2002 UTC revision 1.9, Mon Jun 3 01:25:44 2002 UTC
# Line 61  Line 61 
61  Note, that when you update the Eclipse components from the update site  Note, that when you update the Eclipse components from the update site
62  and restart you may in fact now be running </font><font color="#FF0000">DIFFERENT  and restart you may in fact now be running </font><font color="#FF0000">DIFFERENT
63  CODE THAN WHAT YOU STARTED WITH</font><font color="#000000">. So it is  CODE THAN WHAT YOU STARTED WITH</font><font color="#000000">. So it is
64  really important that you save your starting configuration (scenario steps  really important that you start each of the test scenario steps with a
65  B) and restore it (scenario steps F) when told by the scenario, or any  clean install of eclipse. </font><font color="#FF0000">It is suggested
66  time you have in fact updated the Eclipse Paltform feature (includes the  that you always use a second install of Eclipse running with a different
67  update manager support). </font><font color="#FF0000">It is suggested that  workspace (than what you use to do development) to actually run through
68  you always use a second install of Eclipse running with a different workspace  these scenarios.</font>
 to actually run through these scenarios.</font>  
69  <p><font color="#000000">When openning Bugzilla defects, use the platform/update  <p><font color="#000000">When openning Bugzilla defects, use the platform/update
70  component. Please ALWAYS specify the failing scenario step, and include  component. Please ALWAYS specify the failing scenario step, and include
71  a .zip of the &lt;workspace>/.metadata/ directory</font></td>  a .zip of the &lt;workspace>/.metadata/ directory</font></td>
# Line 485  Line 484 
484  S.3. within the links/ subdirectory, create a file called my.alphabet.link&nbsp;  S.3. within the links/ subdirectory, create a file called my.alphabet.link&nbsp;
485  and add a single line into it</li>  and add a single line into it</li>
486    
487  <p><br>path=&lt;some new install directory>  <br>&nbsp;
488    <p>&nbsp;
489    <p>path=&lt;some new install directory>
490  <p><b>Note</b>: the path should be an absolute path using local file system  <p><b>Note</b>: the path should be an absolute path using local file system
491  syntax. The .link file is loaded as a Java properties file, so on Windows  syntax. The .link file is loaded as a Java properties file, so on Windows
492  you need to double up the back-slashes (eg. path=c:\\temp\\install)  you need to double up the back-slashes (eg. path=c:\\temp\\install)
Legend:
Removed from v.1.8  
changed lines
  Added in v.1.9