platform-update-home/doc/Test Scenarios/eclipse update 3.0.html
Parent Directory
| 
Revision Log
Revision 1.6 - (view) (download) (as text)
| 1 : | dejan | 1.1 | <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
| 2 : | <html> | ||
| 3 : | <head> | ||
| 4 : | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> | ||
| 5 : | <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> | ||
| 6 : | </head> | ||
| 7 : | <body> | ||
| 8 : | |||
| 9 : | <h1> | ||
| 10 : | Scenario: Updating Eclipse Install Using Eclipse Update 3.0</h1> | ||
| 11 : | Last Updated: | ||
| 12 : | dejan | 1.3 | <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%A, %B %d, %Y" startspan -->Friday, May 30, 2003<!--webbot bot="Timestamp" endspan i-CheckSum="24875" --><p> |
| 13 : | dejan | 1.1 | <i>Note: This is the draft of the new test scenarios that are based on 2.1 |
| 14 : | version but take into account redesigned Eclipse Update user interface. Some of | ||
| 15 : | the old functionality may not be available in the new UI, making some scenarios | ||
| 16 : | obsolete. These scenarios will be clearly marked as such.</i></p> | ||
| 17 : | <h3> | ||
| 18 : | Objectives:</h3> | ||
| 19 : | The objective of these scenarios is to illustrate the Eclipse Update 3.0 | ||
| 20 : | function through simple end-to-end use cases. The scenarios are divided | ||
| 21 : | into two parts.<ul> | ||
| 22 : | <li> | ||
| 23 : | Part-1 exercises updating of Eclipse itself from a test site containing | ||
| 24 : | Eclipse builds repackaged as downloadable features. The Eclipse feature | ||
| 25 : | structure is a reasonable representation of a non-trivial product. It contains | ||
| 26 : | a primary feature (the platform) and a number of other features ( jdt, | ||
| 27 : | pde, etc) and is nested.</li> | ||
| 28 : | |||
| 29 : | <li> | ||
| 30 : | Part-2 uses an example "product" to go through the various steps of updating | ||
| 31 : | and extending it using both the Eclipse Update, as well as native installation | ||
| 32 : | (using .zip file containing features and plug-ins that can be extracted | ||
| 33 : | directly into the file system)</li> | ||
| 34 : | |||
| 35 : | <li> | ||
| 36 : | Part-3 uses an even simpler feature hierarchy to go through more advanced | ||
| 37 : | capabilities that include optional features and emergency fixes.</li> | ||
| 38 : | </ul> | ||
| 39 : | |||
| 40 : | <h2> | ||
| 41 : | Part 1: Updating Eclipse - "One Click" Update</h2> | ||
| 42 : | |||
| 43 : | <h3> | ||
| 44 : | Setup:</h3> | ||
| 45 : | Available sites:<ul> | ||
| 46 : | <li> | ||
| 47 : | <a href="http://download.eclipse.org/updates/">http://update.eclipse.org/testUpdates/</a></li> | ||
| 48 : | </ul> | ||
| 49 : | |||
| 50 : | <table BORDER COLS=1 WIDTH="100%" > | ||
| 51 : | <tr> | ||
| 52 : | <td> | ||
| 53 : | <center><b><font color="#FF0000">*** PLEASE READ *** PLEASE READ *** PLEASE | ||
| 54 : | READ *** PLEASE READ ***</font></b></center> | ||
| 55 : | </td> | ||
| 56 : | </tr> | ||
| 57 : | |||
| 58 : | <tr> | ||
| 59 : | <td><font color="#000000">As part of this scenario you will be downloading | ||
| 60 : | and installing various versions of the Eclipse components into the running | ||
| 61 : | Eclipse. The update site is populated with features that have their version | ||
| 62 : | numbers modified as part of the build process. They are generally of the | ||
| 63 : | form 2.0.0.QUALIFIER, where the qualifier differs build to build. Note, | ||
| 64 : | however, that when you install base Eclipse (.zip downloaded from eclipse.org), | ||
| 65 : | all of its features and plug-ins only use 3 part version identifiers (generally | ||
| 66 : | 2.1.0). So all the 2.1.0.Q updates in fact appear more recent that the | ||
| 67 : | build you are running, even though they may in fact be an older build. | ||
| 68 : | Note, that when you update the Eclipse components from the update site | ||
| 69 : | and restart you may in fact now be running </font><font color="#FF0000">DIFFERENT | ||
| 70 : | CODE THAN WHAT YOU STARTED WITH</font><font color="#000000">. So it is | ||
| 71 : | really important that you start each of the test scenario steps with a | ||
| 72 : | <b>clean install of eclipse</b>. </font><font color="#FF0000">It is suggested | ||
| 73 : | that you always use a second install of Eclipse running with a different | ||
| 74 : | workspace (than what you use to do development) to actually run through | ||
| 75 : | these scenarios.</font><p><font color="#000000">When opening Bugzilla defects, use the | ||
| 76 : | Platform/Update | ||
| 77 : | component. Please ALWAYS specify the failing scenario step, and include | ||
| 78 : | a .zip of the <workspace>/.metadata/ directory</font></td> | ||
| 79 : | </tr> | ||
| 80 : | </table> | ||
| 81 : | |||
| 82 : | <h3> | ||
| 83 : | Steps:</h3> | ||
| 84 : | |||
| 85 : | <ul> | ||
| 86 : | <li> | ||
| 87 : | Install second copy of Eclipse to run these scenarios ... do not use your | ||
| 88 : | development copy of Eclipse for this.</li> | ||
| 89 : | |||
| 90 : | <li> | ||
| 91 : | either use the default workspace created by the second Eclipse copy, or | ||
| 92 : | specify (-data) a new workspace for these scenarios</li> | ||
| 93 : | </ul> | ||
| 94 : | |||
| 95 : | <h4> | ||
| 96 : | A. Startup new Eclipse</h4> | ||
| 97 : | |||
| 98 : | <ul> | ||
| 99 : | <li> | ||
| 100 : | A.1. startup Eclipse. On the initial startup with new workspace you should | ||
| 101 : | see the splash come up, be taken down down, and come up again before it | ||
| 102 : | is finally taken down before the Workbench appears. This is due to Eclipse | ||
| 103 : | restart when new features are detected on startup.</li> | ||
| 104 : | |||
| 105 : | <li> | ||
| 106 : | dejan | 1.2 | A.2 go to <b>Help>About</b> and click [Feature Details] and [Plug-in Details] |
| 107 : | dejan | 1.1 | to see more details of what is actually running. Note the baseline version |
| 108 : | of the various items (most will be 2.1.0)</li> | ||
| 109 : | |||
| 110 : | <li> | ||
| 111 : | dejan | 1.2 | A.3. go to <b>Help> Software Updates> Configuration Manager</b> and verify that the features |
| 112 : | dejan | 1.1 | corresponding to the baseline install appear in the "Eclipse Platform" root |
| 113 : | node.</li> | ||
| 114 : | </ul> | ||
| 115 : | |||
| 116 : | <h4> | ||
| 117 : | <font color="#FF00FF">B. Save baseline configuration [cannot be done in the new | ||
| 118 : | UI]</font></h4> | ||
| 119 : | |||
| 120 : | <ul> | ||
| 121 : | <li> | ||
| 122 : | <font color="#FF00FF">B.1. in "Configuration" view, expand "Configuration History"</font></li> | ||
| 123 : | |||
| 124 : | <li> | ||
| 125 : | <font color="#FF00FF">B.2. select the current configuration (at this point it should be the only | ||
| 126 : | one)</font></li> | ||
| 127 : | |||
| 128 : | <li> | ||
| 129 : | <font color="#FF00FF">B.3. popup menu, Save</font></li> | ||
| 130 : | |||
| 131 : | <li> | ||
| 132 : | <font color="#FF00FF">B.4. expand "Saved Configurations"</font></li> | ||
| 133 : | |||
| 134 : | <li> | ||
| 135 : | <font color="#FF00FF">B.5. select the configuration you have just saved</font></li> | ||
| 136 : | |||
| 137 : | <li> | ||
| 138 : | <font color="#FF00FF">B.6. popup, Properties, change name to "Baseline"</font></li> | ||
| 139 : | |||
| 140 : | <li> | ||
| 141 : | <font color="#FF00FF">B.7 close Update Manager</font></li> | ||
| 142 : | </ul> | ||
| 143 : | |||
| 144 : | <h4> | ||
| 145 : | C. "One Click" update</h4> | ||
| 146 : | |||
| 147 : | <ul> | ||
| 148 : | <li> | ||
| 149 : | C.0. NOTE: you must be connected to the network with access to www.eclipse.org | ||
| 150 : | to perform this step. You will be downloading a full Eclipse SDK drop as part of | ||
| 151 : | this step. So you should have a reasonably fast network connection for this | ||
| 152 : | step. In addition, since 'official' Eclipse update site contains only final | ||
| 153 : | releases, we must redirect update search to pick up integration builds from the | ||
| 154 : | test update site. To do so, open <b>Window>Preferences>Install/Update>Automatic | ||
| 155 : | Updates</b> and paste the following URL into the address mappings entry:<br> | ||
| 156 : | <br> | ||
| 157 : | <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/redir.properties"> | ||
| 158 : | http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/redir.properties</a><br> | ||
| 159 : | </li> | ||
| 160 : | |||
| 161 : | <li> | ||
| 162 : | dejan | 1.2 | C.1. select <b>Help>Software Updates>New Updates (Experimental)</b></li> |
| 163 : | dejan | 1.1 | |
| 164 : | <li> | ||
| 165 : | C.2. Make sure that 'Search for updates of the currently installed features' | ||
| 166 : | radio button is selected (the default)</li> | ||
| 167 : | |||
| 168 : | <li> | ||
| 169 : | C.3. wait while eclipse is searching for new updates</li> | ||
| 170 : | |||
| 171 : | <li> | ||
| 172 : | C.3. the search results page should display a new version of eclipse SDK | ||
| 173 : | dejan | 1.2 | pre-selected</li> |
| 174 : | dejan | 1.1 | |
| 175 : | <li> | ||
| 176 : | C.3.1. accept any license agreements</li> | ||
| 177 : | |||
| 178 : | <li> | ||
| 179 : | C.4. click [Finish] and proceed to install the update. When you see feature | ||
| 180 : | verification dialog, click [Install].</li> | ||
| 181 : | |||
| 182 : | <li> | ||
| 183 : | C.5. when you complete the installation, you'll be prompted to restart. | ||
| 184 : | Select [Yes] to restart the platform.</li> | ||
| 185 : | |||
| 186 : | <li> | ||
| 187 : | C.6. workbench should restart automatically</li><ul> | ||
| 188 : | <li> | ||
| 189 : | <b>PLEASE NOTE</b>: at this point you are no longer executing the update | ||
| 190 : | manager code you started with, but rather are running a version of the | ||
| 191 : | update manager that was contained in the update (along with the rest of | ||
| 192 : | the platform plug-ins). Depending on what the update site contained at that | ||
| 193 : | point (changes build to build) the platform may not even restart, and you | ||
| 194 : | may need to reinstall eclipse to continue. Report defects for this (to | ||
| 195 : | make sure there is not actually a legitimate problem) but please be clear | ||
| 196 : | that you failed in step C.6.</li> | ||
| 197 : | </ul> | ||
| 198 : | |||
| 199 : | <li> | ||
| 200 : | C.7. go to Help> About> [Plug-In Details] and [Feature Details] to verify | ||
| 201 : | you are running new version of the platform (the versions for the items | ||
| 202 : | will be 2.1.0.<qualifier>)</li> | ||
| 203 : | |||
| 204 : | <li> | ||
| 205 : | dejan | 1.2 | C.8. Go to Help> Software Updates> Configuration Manager, expand "Current Configuration" |
| 206 : | dejan | 1.1 | and verify you now recognize the new version of the platform that was updated</li> |
| 207 : | </ul> | ||
| 208 : | |||
| 209 : | <h4> | ||
| 210 : | D. Restoring Original Configuration</h4> | ||
| 211 : | |||
| 212 : | <ul> | ||
| 213 : | <li> | ||
| 214 : | D.1. Select <b>Help>Software Updates>Configuration Manager</b> to open the | ||
| 215 : | configuration manager window.</li> | ||
| 216 : | <li> | ||
| 217 : | D.2 Select the current configuration object (the root node) and choose 'Revert | ||
| 218 : | dejan | 1.2 | to previous' (alternatively, select the link with the same name from the list of tasks |
| 219 : | dejan | 1.1 | on the right).</li> |
| 220 : | |||
| 221 : | <li> | ||
| 222 : | D.3. When the wizard opens, a list of past configurations should show up (sorted | ||
| 223 : | dejan | 1.2 | by date in descending order). The previous configuration (first from the top) |
| 224 : | will be pre-selected.</li> | ||
| 225 : | dejan | 1.1 | |
| 226 : | <li> | ||
| 227 : | D.4. press [Finish]</li> | ||
| 228 : | |||
| 229 : | <li> | ||
| 230 : | D.5. A message about required workbench restart will open. Accept it.</li> | ||
| 231 : | |||
| 232 : | <li> | ||
| 233 : | dejan | 1.2 | D.6. workbench should restart automatically. Open Configuration Manager again. |
| 234 : | dejan | 1.1 | <font color="#FF00FF">[note: we should investigate if we can remember the state |
| 235 : | and do this automatically]</font></li> | ||
| 236 : | |||
| 237 : | <li> | ||
| 238 : | D.7. expand the root node and verify all configured features | ||
| 239 : | are the baseline feature versions (generally 2.1.0)</li> | ||
| 240 : | |||
| 241 : | <li> | ||
| 242 : | D.8. click "Show Disabled Features" button in the toolbar of the Configuration | ||
| 243 : | Manager. Observe the updated version as disabled.</li> | ||
| 244 : | |||
| 245 : | <li> | ||
| 246 : | D.9. go to <b>Help>About</b> dialog, [Plug-In Details] and verify you are in | ||
| 247 : | dejan | 1.2 | fact running the baseline plug-ins (all 2.1.0, except for the "special cases" |
| 248 : | dejan | 1.1 | like Xerces, Ant, Lucene, Tomcat, etc)</li> |
| 249 : | |||
| 250 : | <li> | ||
| 251 : | D.10. shut down the workbench</li> | ||
| 252 : | </ul> | ||
| 253 : | |||
| 254 : | <h2> | ||
| 255 : | Part 2: Alphabet Soup</h2> | ||
| 256 : | |||
| 257 : | <h3> | ||
| 258 : | Setup:</h3> | ||
| 259 : | Available sites: | ||
| 260 : | <ul> | ||
| 261 : | <li> | ||
| 262 : | <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/index.html">http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/</a></li> | ||
| 263 : | </ul> | ||
| 264 : | The above site contains pre-built features used as part of the following | ||
| 265 : | scenario steps. It also includes several .zip files (containing features | ||
| 266 : | and plug-ins) that are used to simulate native installer steps.<br> | ||
| 267 : | <table BORDER COLS=1 WIDTH="100%" > | ||
| 268 : | <tr> | ||
| 269 : | <td> | ||
| 270 : | <center><b><font color="#FF0000">*** PLEASE READ *** PLEASE READ *** PLEASE | ||
| 271 : | READ *** PLEASE READ ***</font></b></center> | ||
| 272 : | </td> | ||
| 273 : | </tr> | ||
| 274 : | |||
| 275 : | <tr> | ||
| 276 : | <td><font color="#000000">When opening Bugzilla defects, use the Platform/Update | ||
| 277 : | component. Please ALWAYS specify the failing scenario step, and include | ||
| 278 : | a .zip of the <workspace>/.metadata/ directory</font></td> | ||
| 279 : | </tr> | ||
| 280 : | </table> | ||
| 281 : | |||
| 282 : | <h3> | ||
| 283 : | Description:</h3> | ||
| 284 : | The Alphabet Soup is a simple application packaged as an Eclipse product, | ||
| 285 : | plus several extensions. The application installs a tool button, and a | ||
| 286 : | menu ("Alphabet Soup") that can be used to query the content of the "soup | ||
| 287 : | bowl" and interact with the individual installed "letters" (each letter | ||
| 288 : | in the bowl corresponds to a separate plug-in) | ||
| 289 : | <ul> | ||
| 290 : | <li> | ||
| 291 : | base product is a nested feature, my.alphabet, containing two sub-features | ||
| 292 : | with base sets of "letters"</li> | ||
| 293 : | |||
| 294 : | <li> | ||
| 295 : | 3 extension features containing additional "letters" (plug-ins). The features | ||
| 296 : | have a dependency relationship as follows:</li> | ||
| 297 : | |||
| 298 : | <ul> | ||
| 299 : | <li> | ||
| 300 : | "round letters" extension pack requires the base to be installed</li> | ||
| 301 : | |||
| 302 : | <li> | ||
| 303 : | "straight letters" extension pack requires "round letters" extension pack | ||
| 304 : | to be installed</li> | ||
| 305 : | |||
| 306 : | <li> | ||
| 307 : | "numbers" extension pack requires both "round letters" extension pack and | ||
| 308 : | "straight letters" extension pack to be installed</li> | ||
| 309 : | </ul> | ||
| 310 : | </ul> | ||
| 311 : | Just follow the steps and you'll get the idea.<h3> | ||
| 312 : | Steps:</h3> | ||
| 313 : | |||
| 314 : | <ul> | ||
| 315 : | <li> | ||
| 316 : | Install second copy of Eclipse to run these scenarios ... do not use your | ||
| 317 : | development copy of Eclipse for this.</li> | ||
| 318 : | |||
| 319 : | <li> | ||
| 320 : | either use the default workspace created by the second Eclipse copy, or | ||
| 321 : | specify (-data) a new workspace for these scenarios</li> | ||
| 322 : | </ul> | ||
| 323 : | |||
| 324 : | <h4> | ||
| 325 : | O. Completing the install</h4> | ||
| 326 : | |||
| 327 : | <ul> | ||
| 328 : | <li> | ||
| 329 : | O.1. after you have installed baseline eclipse, unzip the Alphabet Soup | ||
| 330 : | product features from <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/my.alphabet_1.0.0.zip">my.alphabet_1.0.0.zip</a> | ||
| 331 : | into the eclipse/ installation directory. The unzip should overwrite the | ||
| 332 : | install.ini file that is packaged with Eclipse (sets the Alphabet Soup | ||
| 333 : | feature as the primary feature). The product feature .zips can be found | ||
| 334 : | in <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/">http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/</a></li> | ||
| 335 : | |||
| 336 : | <li> | ||
| 337 : | O.2. start eclipse .... after "Completing the install ..." the platform | ||
| 338 : | restarts as "Alphabet Soup" application (own Welcome, About)</li> | ||
| 339 : | |||
| 340 : | <li> | ||
| 341 : | O.3. Click on the "Alphabet Soup" button in the tool bar ... you should | ||
| 342 : | have letters A, B, C and E (all 1.0.0) in your bowl.</li> | ||
| 343 : | |||
| 344 : | <li> | ||
| 345 : | O.4. Go to the "Alphabet Soup" menu and verify you can interact with each | ||
| 346 : | letter (one action per letter on the menu)</li> | ||
| 347 : | |||
| 348 : | <li> | ||
| 349 : | dejan | 1.2 | O.5. Open Help> Software Updates> Configuration Manager</li> |
| 350 : | dejan | 1.1 | |
| 351 : | <li> | ||
| 352 : | dejan | 1.2 | O.6. Expand "Alphabet Soup". Verify "Alphabet Soup 1.0.0" is configured, |
| 353 : | dejan | 1.1 | and it contains 2 sub-features (Round and Straight letters)</li> |
| 354 : | |||
| 355 : | <li> | ||
| 356 : | dejan | 1.2 | O.7. click on each of the features and view more details about each feature |
| 357 : | (double-click for Properties, follow 'More Info...' hyperlink etc.).</li> | ||
| 358 : | dejan | 1.1 | |
| 359 : | <li> | ||
| 360 : | O.8. select "Alphabet Soup 1.0.0" and press [Disable]. You should be notified | ||
| 361 : | that you cannot disable the primary feature (if this is not the case, [Cancel] | ||
| 362 : | the disable action and report a defect).</li> | ||
| 363 : | </ul> | ||
| 364 : | |||
| 365 : | <h4> | ||
| 366 : | dejan | 1.2 | P. Updating the primary feature using new updates wizard</h4> |
| 367 : | dejan | 1.1 | |
| 368 : | <ul> | ||
| 369 : | <li> | ||
| 370 : | dejan | 1.2 | P.1. Open <b>Help>Software Updates>New Updates</b>. Select 'Search for new |
| 371 : | features to install'. Check "Alphabet Soup Update Site" from the list and expand | ||
| 372 : | it. Uncheck all categories except "Alphabet Soup". Press 'Next'.</li> | ||
| 373 : | dejan | 1.1 | |
| 374 : | <li> | ||
| 375 : | dejan | 1.2 | P.2. When the search is over, you should see three versions Alphabet Soup: |
| 376 : | 1.0.1, 1.1.0 and 2.0.0.</li> | ||
| 377 : | dejan | 1.1 | |
| 378 : | <li> | ||
| 379 : | dejan | 1.2 | P.3. Select "Alphabet Soup 1.0.1" and press 'Next'. Go through the install |
| 380 : | dejan | 1.1 | wizard accepting defaults.</li> |
| 381 : | |||
| 382 : | <li> | ||
| 383 : | dejan | 1.2 | P.4. Restart the workbench when prompted. Open Configuration Manager.</li> |
| 384 : | dejan | 1.1 | |
| 385 : | <li> | ||
| 386 : | dejan | 1.2 | P.5. Expand "Alphabet Soup" .... verify you now have Alphabet Soup |
| 387 : | dejan | 1.1 | 1.0.1 installed and configured.</li> |
| 388 : | |||
| 389 : | <li> | ||
| 390 : | P.6. Click the "Show disabled features" filter button .... should see both | ||
| 391 : | versions (one enabled, the other disabled (icon with red "stop" | ||
| 392 : | overlay))</li> | ||
| 393 : | |||
| 394 : | <li> | ||
| 395 : | P.7. click the "Alphabet Soup" tool button ... should show new versions | ||
| 396 : | of the base letters (1.0.1). The actions on "Alphabet Soup" menu should | ||
| 397 : | also indicate we are running the new version.</li> | ||
| 398 : | |||
| 399 : | <li> | ||
| 400 : | dejan | 1.2 | P.8. shut down the workbench</li> |
| 401 : | dejan | 1.1 | </ul> |
| 402 : | |||
| 403 : | <h4> | ||
| 404 : | Q. Updating the primary feature using "native" install (.zip)</h4> | ||
| 405 : | |||
| 406 : | <ul> | ||
| 407 : | <li> | ||
| 408 : | Q.1. unzip the Alphabet Soup product features from <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/my.alphabet_1.1.0.zip">my.alphabet_1.1.0.zip</a> | ||
| 409 : | into the eclipse/ installation directory (look into the features/ or plugins/ | ||
| 410 : | subdirectory to verify you see new 1.1.0 versions)</li> | ||
| 411 : | |||
| 412 : | <li> | ||
| 413 : | Q.2. start Eclipse (a.k.a. Alphabet Soup). You'll see the splash coming | ||
| 414 : | up twice as the platform is updating the configuration. Workbench will | ||
| 415 : | come up, with a dialog informing you have changes. Click [OK] to open the | ||
| 416 : | update manager change dialog.</li> | ||
| 417 : | |||
| 418 : | <li> | ||
| 419 : | Q.3. check the change (so it is applied) and press [Finish]</li> | ||
| 420 : | |||
| 421 : | <li> | ||
| 422 : | Q.4. restart the workbench when prompted</li> | ||
| 423 : | |||
| 424 : | <li> | ||
| 425 : | Q.5. click the "Alphabet Soup" tool button and trigger "Alphabet Soup" | ||
| 426 : | menu action to see you have the new version (1.1.0) of the "soup bowl and | ||
| 427 : | letters"</li> | ||
| 428 : | |||
| 429 : | <li> | ||
| 430 : | dejan | 1.2 | Q.6. Open Configuration Manager expand "Alphabet Soup". Should see |
| 431 : | dejan | 1.1 | Alphabet Soup 1.1.0 enabled, and the other 2 disabled (click the |
| 432 : | "Show disabled features").</li> | ||
| 433 : | </ul> | ||
| 434 : | |||
| 435 : | <h4> | ||
| 436 : | <font color="#000000">R. Adding an extension using the update manager</font></h4> | ||
| 437 : | |||
| 438 : | <ul> | ||
| 439 : | <li> | ||
| 440 : | dejan | 1.3 | <font color="#000000">R.1. </font>Open <b>Help>Software Updates>New Updates</b>. Select 'Search for new |
| 441 : | features to install'. Check "Alphabet Soup Update Site" from the list and expand | ||
| 442 : | it. Uncheck all categories except "Alphabet Soup Fun Pack - Round Letters". Press 'Next'.</li> | ||
| 443 : | dejan | 1.1 | |
| 444 : | <li> | ||
| 445 : | dejan | 1.3 | <font color="#000000">R.2. check "Alphabet Soup Round Letters Extension |
| 446 : | Pack 1.0.0" and press [Next]. Accept defaults in wizard and [Finish]. | ||
| 447 : | dejan | 1.1 | Restart workbench when prompted.</font></li> |
| 448 : | |||
| 449 : | <li> | ||
| 450 : | <font color="#000000">R.3. click of the "Alphabet Soup" tool button and | ||
| 451 : | interact with "Alphabet Soup" menu to see new round letters (D and G). | ||
| 452 : | <b>Note:</b> | ||
| 453 : | may need to go to Window> Customize Perspective...> Other and select the | ||
| 454 : | action sets for the new letters</font></li> | ||
| 455 : | |||
| 456 : | <li> | ||
| 457 : | dejan | 1.3 | <font color="#000000">R.4. open Configuration Manager and verify the |
| 458 : | dejan | 1.1 | new feature is showing as configured.</font></li> |
| 459 : | |||
| 460 : | <li> | ||
| 461 : | dejan | 1.3 | <font color="#000000">R.5. close the Configuration Manager and shut down the workbench</font></li> |
| 462 : | dejan | 1.1 | </ul> |
| 463 : | |||
| 464 : | <h4> | ||
| 465 : | <font color="#000000">S. Adding an extension using "native" install (.zip) | ||
| 466 : | and link file</font></h4> | ||
| 467 : | |||
| 468 : | <ul> | ||
| 469 : | <li> | ||
| 470 : | <font color="#000000">S.0. <b>Note</b>: the first 3 steps will typically | ||
| 471 : | be performed by a native installer. Since you are simulating these steps | ||
| 472 : | you need to do this manually.</font></li> | ||
| 473 : | |||
| 474 : | <li> | ||
| 475 : | <font color="#000000">S.1. Set up a new install directory somewhere in | ||
| 476 : | your file system. Create eclipse/ subdirectory under it. U</font>nzip the | ||
| 477 : | Alphabet Soup Straight Letters extension from <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/my.alphabet.more.straight.letters_1.0.0.zip">my.alphabet.more.straight.letters_1.0.0.zip</a> | ||
| 478 : | into the eclipse/ subdirectory. You should end up with</li> | ||
| 479 : | |||
| 480 : | <ul> | ||
| 481 : | <li> | ||
| 482 : | <some new install directory>/</li> | ||
| 483 : | |||
| 484 : | <br> eclipse/ | ||
| 485 : | <br> | ||
| 486 : | features/ | ||
| 487 : | <br> | ||
| 488 : | plugins/</ul> | ||
| 489 : | |||
| 490 : | <li> | ||
| 491 : | S.2. In the original eclipse install (the one that contains the platform | ||
| 492 : | and Alphabet Soup), create a new directory called "links" as a peer to | ||
| 493 : | features/ and plugins/. You should end up with</li> | ||
| 494 : | |||
| 495 : | <ul> | ||
| 496 : | <li> | ||
| 497 : | <eclipse platform install directory>/</li> | ||
| 498 : | |||
| 499 : | <br> eclipse/ | ||
| 500 : | <br> | ||
| 501 : | links/ | ||
| 502 : | <br> features/ | ||
| 503 : | <br> | ||
| 504 : | plugins/</ul> | ||
| 505 : | |||
| 506 : | <li>S.3. within the links/ subdirectory, create a file called my.alphabet.link | ||
| 507 : | and add a single line into it</li> <br> | ||
| 508 : | <br> | ||
| 509 : | <font face="Courier New"> <font size="2">path=<some new | ||
| 510 : | install directory> </font></font> | ||
| 511 : | <p><b>Note</b>: the path should be an absolute path using local file system | ||
| 512 : | syntax. The .link file is loaded as a Java properties file, so on Windows | ||
| 513 : | you need to double up the back-slashes (e.g. path=c:\\temp\\install) </li> | ||
| 514 : | <li> | ||
| 515 : | S.4. start eclipse (Alphabet Soup). You'll see the splash coming up twice | ||
| 516 : | as the platform is updating the configuration. Workbench will come up, | ||
| 517 : | dejan | 1.3 | with a dialog informing you have changes. Click [OK] to open the Pending Changes dialog.</li> |
| 518 : | dejan | 1.1 | |
| 519 : | <li> | ||
| 520 : | S.5. check the change (so it is applied) and press [Finish]</li> | ||
| 521 : | |||
| 522 : | <li> | ||
| 523 : | S.6. restart the workbench when prompted</li> | ||
| 524 : | |||
| 525 : | <li> | ||
| 526 : | S.7. click the "Alphabet Soup" tool button and trigger "Alphabet Soup" | ||
| 527 : | menu action to see you have the new letters.</li> | ||
| 528 : | |||
| 529 : | <br><b>Note</b>: may need to go to Window> Customize Perspective...> Other | ||
| 530 : | and select the new letters to get the menu actions to become visible | ||
| 531 : | <br><b>Note</b>: if you are following all the steps in the scenario, the | ||
| 532 : | base letters (A, B, C, E) should be at 1.1.0, and the extensions (D, G) | ||
| 533 : | (F, H) at 1.0.0 | ||
| 534 : | <li> | ||
| 535 : | dejan | 1.3 | S.8. Open Configuration Manager and expand "Alphabet Soup". You should see |
| 536 : | a new site representing the extension install (different icon), and it should contain the | ||
| 537 : | dejan | 1.1 | extension feature you've installed.</li> |
| 538 : | <li> | ||
| 539 : | S.9. Click on the new extension, and disable it in the Preview view. After | ||
| 540 : | restart, verify that all the features and plug-ins from the extension are | ||
| 541 : | missing. Enable it and verify that they are back after the restart.</li> | ||
| 542 : | </ul> | ||
| 543 : | |||
| 544 : | <h4> | ||
| 545 : | dejan | 1.3 | <font color="#FF00FF">T. Installing another extension using the update manager (with environment |
| 546 : | filtering) [this cannot be done with the new UI]</font></h4> | ||
| 547 : | dejan | 1.1 | |
| 548 : | <ul> | ||
| 549 : | <li> | ||
| 550 : | dejan | 1.3 | <font color="#FF00FF">T.1. expand "Sites to Visit", "Alphabet Soup Update |
| 551 : | dejan | 1.1 | Site", "Alphabet Soup Fun Pack - Numbers"</font></li> |
| 552 : | |||
| 553 : | <li> | ||
| 554 : | dejan | 1.3 | <font color="#FF00FF">T.2. The Numbers extension specifies an OS in its |
| 555 : | dejan | 1.1 | feature definition. The update site contains features for Win and Linux. |
| 556 : | On those two platforms you should see a list of features designated for | ||
| 557 : | than platform. On other platforms you are out of luck ... you don't get | ||
| 558 : | to play with numbers (skip the rest of this step)</font></li> | ||
| 559 : | |||
| 560 : | <li> | ||
| 561 : | dejan | 1.3 | <font color="#FF00FF">T.3. uncheck the "Show matching features only" filter |
| 562 : | dejan | 1.1 | .... should now see all the features for both platforms. Check the filter |
| 563 : | back again.</font></li> | ||
| 564 : | |||
| 565 : | <li> | ||
| 566 : | dejan | 1.3 | <font color="#FF00FF">T.4. select "Alphabet Soup Numbers Extension Pack |
| 567 : | dejan | 1.1 | for <OS>1.0.1" and click [Install]. Accept defaults in wizard. In the |
| 568 : | location selection page ensure the extension location created in steps | ||
| 569 : | S is not offered as a choice. Press [Finish]. Restart workbench when prompted.</font></li> | ||
| 570 : | |||
| 571 : | <li> | ||
| 572 : | dejan | 1.3 | <font color="#FF00FF">T.5. click of the "Alphabet Soup" tool button and |
| 573 : | dejan | 1.1 | interact with "Alphabet Soup" menu to see new numbers (3 and 5). <b>Note:</b> |
| 574 : | may need to go to Window> Customize Perspective...> Other and select the | ||
| 575 : | action sets for the new numbers</font></li> | ||
| 576 : | |||
| 577 : | <li> | ||
| 578 : | dejan | 1.3 | <font color="#FF00FF">T.6. expand Current Configuration and verify the |
| 579 : | dejan | 1.1 | new feature is showing as configured in the original install site</font></li> |
| 580 : | |||
| 581 : | <li> | ||
| 582 : | dejan | 1.3 | <font color="#FF00FF">T.7. close the update manager and shut down the workbench</font></li> |
| 583 : | dejan | 1.1 | </ul> |
| 584 : | |||
| 585 : | <h4> | ||
| 586 : | <font color="#000000">"Free-form" testing</font></h4> | ||
| 587 : | |||
| 588 : | <ul> | ||
| 589 : | <li> | ||
| 590 : | <font color="#000000">the above scenarios describe a path through the update | ||
| 591 : | support. Run through it once as described. There is lot's of opportunity | ||
| 592 : | dejan | 1.3 | to do thing in different order, click on other buttons, try other features |
| 593 : | dejan | 1.1 | in the UI. Go ahead an explore. Remember, is you see something that does |
| 594 : | not work, is not correct, or is not what you'd expected, open Bugzilla | ||
| 595 : | defects in the platform/update component. Please ALWAYS specify the steps | ||
| 596 : | leading up to the failure, and include a .zip of the <workspace>/.metadata/ | ||
| 597 : | directory</font></li> | ||
| 598 : | </ul> | ||
| 599 : | |||
| 600 : | <h2> | ||
| 601 : | Part 3: Optional features and e-fixes</h2> | ||
| 602 : | |||
| 603 : | <h3> | ||
| 604 : | Setup:</h3> | ||
| 605 : | <p>Available sites:</p> | ||
| 606 : | <ul> | ||
| 607 : | <li> | ||
| 608 : | <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/optionalSite/">http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/</a></li> | ||
| 609 : | </ul> | ||
| 610 : | <p>The above site contains pre-built features used as part of the following | ||
| 611 : | scenario steps.<br> </p> | ||
| 612 : | <table BORDER COLS=1 WIDTH="100%" > | ||
| 613 : | <tr> | ||
| 614 : | <td> | ||
| 615 : | <center> | ||
| 616 : | <p><b><font color="#FF0000">*** PLEASE READ *** PLEASE READ *** PLEASE | ||
| 617 : | READ *** PLEASE READ ***</font></b></p> | ||
| 618 : | </center> | ||
| 619 : | </td> | ||
| 620 : | </tr> | ||
| 621 : | |||
| 622 : | <tr> | ||
| 623 : | <td><font color="#000000">When opening Bugzilla defects, use the Platform/Update | ||
| 624 : | component. Please ALWAYS specify the failing scenario step, and include | ||
| 625 : | a .zip of the <workspace>/.metadata/ directory. Note that we ran out of | ||
| 626 : | letters, so we are starting from A again. You need to include the part number | ||
| 627 : | when specifying steps (e.g. 3.A7)</font></td> | ||
| 628 : | </tr> | ||
| 629 : | </table> | ||
| 630 : | |||
| 631 : | <h3> | ||
| 632 : | Description:</h3> | ||
| 633 : | <p>The Optional Site is a simple site that contains several versions of the | ||
| 634 : | 'Root' feature. The feature includes another feature (XYZBogus) that in turn | ||
| 635 : | includes features XYZ and Bogus. The last two features are included as optional, | ||
| 636 : | which means that users can elect not to install them. Several interesting | ||
| 637 : | consequences result from this capability, and this part deals with them.</p> | ||
| 638 : | <p>The site also contains several e-fixes. E-fix is a feature that is designed | ||
| 639 : | to patch another feature with an exact ID and version. It is used to deliver | ||
| 640 : | temporary fixes between full root updates.</p> | ||
| 641 : | <h2>A. Installing feature Root 1.0.0</h2> | ||
| 642 : | dejan | 1.3 | <p>A1. Open New Updates wizard. Select 'Search for new features to install'. |
| 643 : | Press [Add Update Site...] and paste the URL listed above under 'Available | ||
| 644 : | Sites:' (also choose some name).<br> | ||
| 645 : | A2. Check the newly created site and press [Next]. Check the feature Root 1.0.0 | ||
| 646 : | from the list of results. Press [Next].<br> | ||
| 647 : | dejan | 1.1 | A3. Accept the license in the License page.<br> |
| 648 : | A4. Uncheck 'XYZ 1.0.0' optional feature in the Optional Features page. Leave | ||
| 649 : | 'Bogus 1.0.0' feature selected.<br> | ||
| 650 : | A5. Install (accept unsigned feature). Restart.<br> | ||
| 651 : | dejan | 1.3 | A6. Using Configuration Manager, verify that 'Root 1.0.0' feature has been installed and that 'XYZ 1.0.0' is |
| 652 : | missing.<br> | ||
| 653 : | A7. Verify that | ||
| 654 : | dejan | 1.1 | 'XYZ 1.0.0' is shown and marked as '(not installed')<br> |
| 655 : | A8. If you want to stop being warned about unsigned features, toggle the option | ||
| 656 : | off in the Install/Update preferences. Verify that you are warned about the | ||
| 657 : | consequences (rogue features deleting your entire hard drive and such).</p> | ||
| 658 : | <h2>B. Updating Root 1.0.0 to Root 1.0.1</h2> | ||
| 659 : | dejan | 1.3 | <p>B1. Open New Updates wizard. Select 'Search for new features to install'. |
| 660 : | Check 'Optional site' created in A1. Press [Next]. Verify that 'Root 1.0.0' is | ||
| 661 : | not present (should be filtered out since it is already installed). Check 'Root 1.0.1'. | ||
| 662 : | Press [Next].<br> | ||
| 663 : | dejan | 1.1 | B2. After accepting the license, verify that features 'XYZBogus' and 'Bogus' are |
| 664 : | checked and grayed out in 'Optional Features' page, while 'XYZ' plug-ins is | ||
| 665 : | dejan | 1.3 | unchecked (leave it unchecked). Install and restart.</p> |
| 666 : | dejan | 1.5 | <p><font color="#0000FF">Bug #38270: |
| 667 : | dejan | 1.6 | <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=38270">[new UI] Part |
| 668 : | 3,B2: Bogus is not grayed out, XYZ is checked in the Optional Features page</a></font></p> | ||
| 669 : | dejan | 1.3 | <p>B3. Using Configuration Manager, verify that we now have Root 1.0.1 installed that is still without XYZ |
| 670 : | feature (XYZ 1.0.1 shows as 'not installed').</p> | ||
| 671 : | dejan | 1.1 | <h2>C. Preserving the state of the optional feature</h2> |
| 672 : | <p>C1. Close Eclipse. Manually delete all 'com.example.*' features from the | ||
| 673 : | features/ directory and all 'com.example.*' plug-ins from the plugins/ | ||
| 674 : | directory. Delete the '.config' directory in the .metadata directory of the | ||
| 675 : | workspace (you want to preserve the bookmark).<br> | ||
| 676 : | C2. Repeat scenario A but this time leave all the optional features selected.<br> | ||
| 677 : | C3. Restart and open current configuration. Verify that all the features are | ||
| 678 : | showing as enabled.<br> | ||
| 679 : | C4. Select 'XYZ 1.0.0' feature and select 'Disable' button in the preview. | ||
| 680 : | Restart.<br> | ||
| 681 : | C5. Verify that 'XYZ 1.0.0' feature is now disabled in the 'Root 1.0.0' | ||
| 682 : | hierarchy (you will need to make disabled features visible in the view to do | ||
| 683 : | dejan | 1.3 | that).</p> |
| 684 : | <p>Bug: Part 3,C5: Optional feature XYZ 1.0.0 visible when disabled with the | ||
| 685 : | filter on</p> | ||
| 686 : | <p>C6. Open the New Updates wizard, press [Next], [Next], find Root 1.0.1 feature, | ||
| 687 : | press [Next].<br> | ||
| 688 : | dejan | 1.1 | C7. After accepting the license, leave all settings default and install the new |
| 689 : | version. Restart.<br> | ||
| 690 : | C8. Verify that 'Root 1.0.1' is now installed, and that 'XYZBogus 1.0.1' and | ||
| 691 : | 'Bogus 1.0.1' are showing in the hierarchy. Also verify that 'XYZ 1.0.1' is <b> | ||
| 692 : | installed but disabled </b>(we are testing whether the original state of XYZ | ||
| 693 : | 1.0.0 was preserved during the update). The expected outcome is that the new | ||
| 694 : | version of XYZ is installed but it remains disabled as before.</p> | ||
| 695 : | dejan | 1.6 | <p>Bug #38272: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=38272"> |
| 696 : | [new UI] Part3,C8: Optional feature state is not preserved after update</a></p> | ||
| 697 : | dejan | 1.3 | <h2><font color="#FF00FF">D1. Installing the missing optional feature (from the originating site) |
| 698 : | [cannot be done in the new UI]</font></h2> | ||
| 699 : | <p><font color="#FF00FF">D1.1. Repeat cleanup as in C1.<br> | ||
| 700 : | dejan | 1.1 | D1.2. Repeat the scenario A.<br> |
| 701 : | dejan | 1.3 | D1.3. After the restart, go back to the Updates view and select Root 1.0.0 again. Verify that |
| 702 : | the action button is visible and that the label is "Change". Press it.<br> | ||
| 703 : | dejan | 1.1 | D1.4. When in 'Optional Features' wizard page, ensure that 'Bogus 1.0.0' |
| 704 : | optional feature is checked and grayed out. Select 'XYZ 1.0.0' feature. Finish | ||
| 705 : | the install. Restart.<br> | ||
| 706 : | D1.5. Verify that we now have all the features in 'Root 1.0.0' hierarchy in the | ||
| 707 : | dejan | 1.3 | current configuration.</font></p> |
| 708 : | dejan | 1.1 | <h2>D2. Installing the missing optional feature (using the saved originating |
| 709 : | site URL)</h2> | ||
| 710 : | dejan | 1.3 | <p><font color="#FF00FF">D2.1. After finishing D1., delete XYZ 1.0.0 feature and XYZ 1.0.0 plug-in |
| 711 : | dejan | 1.1 | manually from <b>features</b> and <b>plugins</b> directories, respectively.<br> |
| 712 : | dejan | 1.3 | </font>D2.1(new) Perform D1.1 and D1.2 steps to install Root 1.0.0 without XYZ |
| 713 : | 1.0.0.<br> | ||
| 714 : | D2.2. After restart, open Configuration Manager. Select 'XYZ 1.0.0' feature object (should be | ||
| 715 : | dejan | 1.1 | shown as 'not installed').<br> |
| 716 : | dejan | 1.3 | D2.3. Verify that the 'Install from originating server' hyperlink is shown in the |
| 717 : | list of tasks on the right. Select it.<br> | ||
| 718 : | dejan | 1.1 | D2.4. When the install wizard shows up, follow it until XYZ 1.0.0 plug-in is |
| 719 : | installed. <font color="#0000FF">Cool: missing optional feature reference has a | ||
| 720 : | preserved URL of the originating site that it can use to reconnect and install | ||
| 721 : | it later.</font></p> | ||
| 722 : | dejan | 1.6 | <p><font color="#0000FF">Bug #38273: |
| 723 : | <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=38273">[new UI] Part | ||
| 724 : | 3,D2.3: 'Install from originating server' does not work</a></font></p> | ||
| 725 : | dejan | 1.1 | <h2>E. Discovering missing optional feature</h2> |
| 726 : | <p>E1. Manually copy 'com.example.xyz_1.0.0' from 'features' directory and | ||
| 727 : | 'com.example.xyz_1.0.0' from 'plugins' directory into a temp. place. After that, | ||
| 728 : | repeat cleanup as in C1.<br> | ||
| 729 : | E2. Repeat the scenario A and verify that XYZ 1.0.0 is missing from the | ||
| 730 : | configuration (shown as 'not installed').<br> | ||
| 731 : | E3. Close Eclipse. Manually copy 'com.example.xyz_1.0.0' feature from the temp. | ||
| 732 : | space into the 'features' directory and 'com.example.xyz_1.0.0' plug-in from the | ||
| 733 : | temp. space into the 'plugins' directory. Start Eclipse.<br> | ||
| 734 : | E4. Verify that no dialog was shown and that feature XYZ 1.0.0 was detected and | ||
| 735 : | configured into the hierarchy of 'Root 1.0.0'.</p> | ||
| 736 : | <h2>F. Installing missing optional features natively after updates</h2> | ||
| 737 : | <p>F1. Repeat preservation + cleanup as in E1.<br> | ||
| 738 : | F2. Repeat the scenario A.<br> | ||
| 739 : | dejan | 1.4 | F3. Open the 'New Updates' wizard and select 'Search for updates of the |
| 740 : | currently installed features'. The wizard | ||
| 741 : | should discover feature 'Root 1.0.1' plus some e-fixes. Check Root 1.0.1 only | ||
| 742 : | and press [Next]. Accept the license and finish install. | ||
| 743 : | dejan | 1.1 | Restart.<br> |
| 744 : | F4. At this point, we should have installed Root 1.0.1 with XYZBogus 1.0.1 and | ||
| 745 : | dejan | 1.4 | Bogus 1.0.1, but not XYZ 1.0.1.<br> |
| 746 : | dejan | 1.1 | F5. Manually copy feature XYZ 1.0.0 from the temp space and plug-in XYZ 1.0.0 |
| 747 : | from the temp space as in E3. <br> | ||
| 748 : | F6. At this point, verify that XYZ 1.0.0 is present in the hierarchy of XYZ | ||
| 749 : | 1.0.0 but disabled because Root 1.0.0 is disabled.<br> | ||
| 750 : | dejan | 1.4 | F7. Run the 'one-click' update again as in F3. It should discover Root 1.0.1 |
| 751 : | dejan | 1.1 | again because we now have previous version of XYZ and it can now bring it up to |
| 752 : | dejan | 1.4 | 1.0.1. Reinstall Root 1.0.1 and restart.<br> |
| 753 : | dejan | 1.1 | F8. Verify in the configuration that XYZ 1.0.1 is now installed and enabled.</p> |
| 754 : | dejan | 1.4 | <p><font color="#0000FF">Bug: Part 3,F7: Root 1.0.1 is disabled and XYZ 1.0.1 is |
| 755 : | left orphaned.</font></p> | ||
| 756 : | dejan | 1.1 | <p><font color="#0000FF">Note: as you go through the the scenarios G, H and I |
| 757 : | that deal with e-fixes, it is recommended to increase the coverage by switching | ||
| 758 : | between multiple workspaces (install couple of e-fixes, then start with a new | ||
| 759 : | workspace, install some more, create a new workspace, install some more, than | ||
| 760 : | switch back to the first one). Since state is stored in each workspace, that | ||
| 761 : | will give Update an additional workout to reconcile its state with changes in | ||
| 762 : | the file system (both partial and full reconcilers will kick in).</font></p> | ||
| 763 : | <h2>G1. Cumulative patches</h2> | ||
| 764 : | <p>G1.1 Repeat steps C1, C2 and C3 to install Root 1.0.0 feature hierarchy. | ||
| 765 : | Verify that all Root features (including optional ones) are installed.<br> | ||
| 766 : | G1.2 Expand optional site bookmark in Updates and locate folder "Emergency | ||
| 767 : | Fixes". Locate feature EFIX e334 1.0.0. Select it and install it.<br> | ||
| 768 : | G1.3 After restart, verify that EFIX e334 has been installed and that it | ||
| 769 : | includes XYZ 1.0.0.e334. The same XYZ feature should be included by Root | ||
| 770 : | 1.0.0->XYZ Bogus 1.0.0 (should show up arrow indicating branch update). There | ||
| 771 : | should be no errors or warnings.<br> | ||
| 772 : | G1.4 Expand optional site bookmark in Updates and locate folder "Emergency | ||
| 773 : | Fixes". Locate feature EFIX e335 1.0.0. Select it and install it. <i>Note: e335 | ||
| 774 : | is a cumulative fix because it fixes a problem in XYZ 1.0.0 and also includes a | ||
| 775 : | fix in e334.<br> | ||
| 776 : | </i>G1.5 After restart, verify that e335 has been installed and that it includes | ||
| 777 : | XYZ 1.0.0.e335. The same XYZ feature should be included by Root 1.0.0->XYZ Bogus | ||
| 778 : | 1.0.0 (should show up arrow indicating branch update). <br> | ||
| 779 : | G1.6 <b>The same XYZ 1.0.0.e335 should also show up as a child of EFIX e334</b>. | ||
| 780 : | The interpretation is that XYZ 1.0.0.e335 also includes a fix for e334, so the | ||
| 781 : | fact that the previous version has been disabled does not invalidate EFIX e334.</p> | ||
| 782 : | <h2>G2. Patches that include other patches</h2> | ||
| 783 : | <p>G2.1. Repeat steps C1, C2 and C3 to install Root 1.0.0 feature hierarchy. | ||
| 784 : | Verify that all Root features (including optional ones) are installed.<br> | ||
| 785 : | G2.2. Expand optional site bookmark in Updates and locate folder 'Emergency | ||
| 786 : | Fixes'. Locate feature EFIX e452 1.0.0. Select it and install it.<br> | ||
| 787 : | G2.3. After restart, verify that: EFIX e452 is installed; its child feature e388 | ||
| 788 : | should include Bogus Feature 1.0.0.e388. The same Bogus Feature should be | ||
| 789 : | included by Root 1.0.0 hierarchy. There should be no errors or warnings.<br> | ||
| 790 : | G2.4. Expand 'Saved Configurations' folder. Verify that a backup configuration | ||
| 791 : | for e452 has been created (backup configurations have label in format "@<id_version> | ||
| 792 : | backup".</p> | ||
| 793 : | <h2>H. Updating feature branches with partial patch cleanup</h2> | ||
| 794 : | <p>H1. After installing patch e452 in scenario G2, search for new updates by | ||
| 795 : | selecting 'Window->Updates->New Updates'. <br> | ||
| 796 : | H2. When the update wizard comes up with the results, uncheck the checkbox | ||
| 797 : | 'Filter features included ...'. Uncheck "Root 1.0.1" and check "XYZBogus 1.0.1" | ||
| 798 : | from the list of search results. <font color="#0000FF">Cool: this demonstrates | ||
| 799 : | how branches in the feature hierarchy can be individually updated.</font><br> | ||
| 800 : | H3. Accept the license agreement and install the feature.<br> | ||
| 801 : | H4. After restart, verify that Root 1.0.0 now includes XYZBogus 1.0.1 (<font color="#0000FF">Cool: | ||
| 802 : | XYZBogus 1.0.1 image should have an upward pointing arrow overlay indicating | ||
| 803 : | that the feature has been updated from the original version specified in the | ||
| 804 : | Root 1.0.0 manifest</font>). Also verify that e388 does not show up anywhere, | ||
| 805 : | but EFIX e452 should still be present in the configuration.</p> | ||
| 806 : | <p><font color="#0000FF">Note: Technically, since EFIX e452 includes EFIX e388 | ||
| 807 : | and since e388 is now disabled because XYZBogus 1.0.1 is updated, EFIX e452 | ||
| 808 : | should show error status (missing included feature). Update performs additional | ||
| 809 : | computation in this case to find if e452 is really broken. The fact is that even | ||
| 810 : | though the referenced feature e388 is disabled, it is a patch for XYZBogus 1.0.0 | ||
| 811 : | which has since been upgraded. Updates makes a (daring) assumption that a formal | ||
| 812 : | update for a feature includes all the patches published for a previous version | ||
| 813 : | of that feature. In this particular case, Update assumes that XYZBogus 1.0.1, | ||
| 814 : | being an update to XYZBogus 1.0.0, contains all the fixes registered for | ||
| 815 : | XYZBogus 1.0.0, including e388. It concludes that EFIX e452 will indirectly | ||
| 816 : | satisfy its need for e388 through XYZBogus 1.0.1 code.</font></p> | ||
| 817 : | <h2>I. Updating feature root with patch cleanup</h2> | ||
| 818 : | <p>I1. After updating XYZBogus in scenario H, search for updates again. This | ||
| 819 : | time, accept the default (Root 1.0.1) and install it.<br> | ||
| 820 : | I2. After restart, verify that Root 1.0.1 is installed and that all the included | ||
| 821 : | features are version 1.0.1. Also verify that there are no e-fixes left enabled | ||
| 822 : | in the configuration.<br> | ||
| 823 : | I3. Open file ".install-log" in <workspace>/.metadata/.config/ and verify that | ||
| 824 : | it contains logs of all the activities performed in scenarios G, H and I.</p> | ||
| 825 : | <h2>J. Handling cross-site version conflicts</h2> | ||
| 826 : | <p>The role of this scenario is to show how cross-site conflicts are handled. | ||
| 827 : | Cross-site conflicts are caused by root features in separate install sites that | ||
| 828 : | include features of the same ID but different versions. Since both features will | ||
| 829 : | be configured and their plug-ins contributed to the Eclipse runtime, runtime | ||
| 830 : | will resolve the duplication by selecting plug-ins with the higher version. | ||
| 831 : | Update warns about this 'silent' upgrade when an attempt is made to install or | ||
| 832 : | update a feature that can cause such a conflict to appear.</p> | ||
| 833 : | <ul> | ||
| 834 : | <li>Available sites: <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/extensionSite/">http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/extensionSite/</a></li> | ||
| 835 : | </ul> | ||
| 836 : | <p>J1. Repeat cleanup as in C1.<br> | ||
| 837 : | J2. Select "Optional Site" bookmark as in A1 and install Root 1.0.0 with all the | ||
| 838 : | optional features. Restart.<br> | ||
| 839 : | J3. Add another bookmark called "Extension Site" with the URL as shown above.<br> | ||
| 840 : | J4. Expand the bookmark object and select feature "Root Extension 1.0.0". Press | ||
| 841 : | "Install" button.<br> | ||
| 842 : | J5. Accept the license and select both the optional features for install.<br> | ||
| 843 : | J6. Do not accept the default target install site. Instead, create a new one by | ||
| 844 : | pressing "Add" button. Choose a location outside the Eclipse product tree | ||
| 845 : | (anywhere else on the disk). Press "Finish". Restart.<br> | ||
| 846 : | J7. Verify that the current configuration has two install sites. The first one | ||
| 847 : | should contain Eclipse features and Root 1.0.0. The second one (the one you | ||
| 848 : | picked in J6) should contain Root Product Extension 1.0.0. There should be no | ||
| 849 : | conflicts.<br> | ||
| 850 : | J8. Search for new updates by selecting "Window->Updates->New Updates". You | ||
| 851 : | should get two results: Root 1.0.1 and Root Extension 1.0.1. Uncheck Root 1.0.1. | ||
| 852 : | Press "Next" and accept all other default settings until "Finish" is enabled. | ||
| 853 : | Press Finish".<br> | ||
| 854 : | J9. Verify that a warning dialog is opened explaining the conflict. The conflict | ||
| 855 : | should be caused by XYZ and Bogus features that will be 1.0.0 in one site and | ||
| 856 : | 1.0.1 in another if the update proceeds. Answer "No".<br> | ||
| 857 : | J10. Return back to the first page of the wizard and select both results (Root | ||
| 858 : | 1.0.1 and Root Extension 1.0.1). Advance to the last page and press "Finish" | ||
| 859 : | again. This time, there should be no conflicts because both XYZ and Bogus | ||
| 860 : | features will be simultaneously updated to version 1.0.1.<br> | ||
| 861 : | J11. After restart, verify that the current configuration shows no warning | ||
| 862 : | overlays.</p> | ||
| 863 : | <h2>K. Web-triggered updates</h2> | ||
| 864 : | <p>Update Manager has a neat feature whereby it can run a Web application and | ||
| 865 : | accept calls from a browser with the right URL. Tasks like presentation, search, | ||
| 866 : | classification, user verification etc. can all be handled by the provider's web | ||
| 867 : | site (presumably running a Web application itself). Features and plug-ins are | ||
| 868 : | still in the standard update sites, but these sites are used as feature servers. | ||
| 869 : | When users click on 'Download' or similar buttons or links, a URL query is | ||
| 870 : | composed and sent to Eclipse with the Update Web application running. Update | ||
| 871 : | servlet receives the query and initiates the install process. At this point, we | ||
| 872 : | are in the familiar install wizard.</p> | ||
| 873 : | Available sites: | ||
| 874 : | <ul> | ||
| 875 : | <li><a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-update-home/optionalSite/index.html">http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/index.html</a> | ||
| 876 : | </li> | ||
| 877 : | </ul> | ||
| 878 : | <p>K1. Repeat the cleanup as in C1.<br> | ||
| 879 : | K2. Open "Preferences" dialog and select "Install/Update->Web-triggered updates" | ||
| 880 : | page. Turn the web application on. When pressing "OK" there will be a couple of | ||
| 881 : | seconds delay (starting the Tomcat server).<br> | ||
| 882 : | K3. Open Update Manager and create a new site bookmark using the URL listed | ||
| 883 : | above. When in the wizard, choose the non-default 'Web site' bookmark type. | ||
| 884 : | Finish.<br> | ||
| 885 : | K4. Double-click on the bookmark to cause the External Preview view to open | ||
| 886 : | (note: this is only on Windows; on other platform, the page will open in a | ||
| 887 : | standalone Web browser).<br> | ||
| 888 : | K5. You should see a page with two Download buttons. Press on the Download | ||
| 889 : | button for Root 1.0.0. Verify that a progress monitor dialog opens while | ||
| 890 : | connecting to the feature server. Eventually, Install Wizard should show up. | ||
| 891 : | Follow it to install Root 1.0.0.<br> | ||
| 892 : | K6. After restart, double-click on the Web link again and click on the | ||
| 893 : | 'Download' button for Root 1.0.0. This time, a problem response page should show | ||
| 894 : | up indicating that the requested feature is already installed.<br> | ||
| 895 : | K7. Click on the 'Download' button for the feature Root 1.0.1. This one should | ||
| 896 : | be treated as an update. Follow it to the end and restart.<br> | ||
| 897 : | K8. Verify that the configuration shows the correct features.</p> | ||
| 898 : | |||
| 899 : | <h2>L. Updates view clipboard operations</h2> | ||
| 900 : | |||
| 901 : | <p>L1. The following objects in the Updates view support clipboard operations: | ||
| 902 : | site bookmarks, folders and searches. Spend some time creating new bookmarks, | ||
| 903 : | folders and searches, and rearranging them using both clipboard (cut/copy/paste) | ||
| 904 : | and direct manipulation (drag and drop) methods.</p> | ||
| 905 : | |||
| 906 : | </body> | ||
| 907 : | </html> |
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |