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

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

revision 1.6, Wed May 22 12:51:53 2002 UTC revision 1.7, Sat Jun 1 18:51:04 2002 UTC
# Line 8  Line 8 
8    
9  <h1>  <h1>
10  Scenario: Updating Eclipse Install Using The Update Manager</h1>  Scenario: Updating Eclipse Install Using The Update Manager</h1>
11    &nbsp;
12    <table BORDER COLS=1 WIDTH="100%" >
13    <tr>
14    <td><font color="#FF0000">NOTE: The test scenarios are being updated to
15    match the F2 build structure. At present, only scenario Part 2 (Alphabet
16    Soup) can be tried</font></td>
17    </tr>
18    </table>
19    
20    <p>Last Updated: June 1, 2002 2:45PM&nbsp; .... being updated
21  <h3>  <h3>
22  Objectives:</h3>  Objectives:</h3>
23  The objective of these scenarios is to illustrate the Eclipse update manager  The objective of these scenarios is to illustrate the Eclipse update manager
24  function through simple end-to-end use cases. The scenarios are divided  function through simple end-to-end use cases. The scenarios are divided
25  into three parts.  into two parts.
26  <ul>  <ul>
27  <li>  <li>
28  Part-1 excercises updating of Eclipse itself from a test site containing  Part-1 excercises updating of Eclipse itself from a test site containing
29  Eclipse builds repackaged as downloadable features. The Eclipse feature  Eclipse builds repackaged as downloadable features. The Eclipse feature
30  structure is a reasonable representation of a non-trivial product. It contains  structure is a reasonable representation of a non-trivial product. It contains
31  a primary feature (the platform) and a number of other features ( jdt,  a primary feature (the platform) and a number of other features ( jdt,
32  pde, etc).</li>  pde, etc) and is nested.</li>
33    
34  <li>  <li>
35  Part-2 uses an example "product" to go through the various steps of updating  Part-2 uses an example "product" to go through the various steps of updating
36  and extending it using both the update manager, as well as native installation  and extending it using both the update manager, as well as native installation
37  (using .zip file containing features and plugins that can be extracted  (using .zip file containing features and plugins that can be extracted
38  directly into the file system)</li>  directly into the file system)</li>
   
 <li>  
 Part-3 demonstrates packaging Eclipse as a nested feature and updating  
 it. This scenario test site is not available on the public internet.</li>  
39  </ul>  </ul>
40    
41  <h2>  <h2>
# Line 702  Line 707 
707    
708  <br>&nbsp;  <br>&nbsp;
709  <p>&nbsp;  <p>&nbsp;
710    <br>&nbsp;
711    <br>&nbsp;
712  <p>path=&lt;some new install directory>  <p>path=&lt;some new install directory>
713  <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
714  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
Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7