Scenario: Updating Eclipse Install Using The Update Manager

Objectives:

• Part-1 exercises updating of Eclipse itself from a test site containing Eclipse builds repackaged as downloadable features. The Eclipse feature structure is a reasonable representation of a non-trivial product. It contains a primary feature (the platform) and a number of other features ( jdt, pde, etc) and is nested.
• Part-2 uses an example "product" to go through the various steps of updating and extending it using both the update manager, as well as native installation (using .zip file containing features and plug-ins that can be extracted directly into the file system)
• Part-3 uses an even simpler feature hierarchy to go through more advanced capabilities that include optional features and emergency fixes.

Part 1: Updating Eclipse - "One Click" Update

Setup:

• http://update.eclipse.org/testUpdates/

Steps:

• Install second copy of Eclipse to run these scenarios ... do not use your development copy of Eclipse for this.
• either use the default workspace created by the second Eclipse copy, or specify (-data) a new workspace for these scenarios

A. Startup new Eclipse

• A.1. startup Eclipse. On the initial startup with new workspace you should see the splash come up, be taken down down, and come up again before it is finally taken down before the Workbench appears. This is due to Eclipse restart when new features are detected on startup.
• A.2 go to Help> About and click [Feature Details] and [Plug-in Details] to see more details of what is actually running. Note the baseline version of the various items (most will be 2.1.0)
• A.3. go to Help> Software Updates> Update Manager and verify that the features corresponding to the baseline install appear in the "Current Configuration"

B. Save baseline configuration

• B.1. in "Configuration" view, expand "Configuration History"
• B.2. select the current configuration (at this point it should be the only one)
• B.3. popup menu, Save
• B.4. expand "Saved Configurations"
• B.5. select the configuration you have just saved
• B.6. popup, Properties, change name to "Baseline"
• B.7 close Update Manager

C. "One Click" update

• C.0. NOTE: you must be connected to the network with access to www.eclipse.org to perform this step. You will be downloading a full Eclipse SDK drop as part of this step. So you should have a reasonably fast network connection for this step. In addition, Eclipse features all point to http://update.eclipse.org/updates/ as the official update site. For our testing purposes, you must use the test update site (http://update.eclipse.org/testUpdates/). Add this site as a bookmark in Updates view and change the scope settings for the 'Available Updates' search object to include bookmarked sites. This is a trick that allows the search for find results in the subsequent steps.
• C.1. select Help> Software Updates> New Updates
• C.2. wait while eclipse is searching for new updates
• C.3. the search results page should display a new version of eclipse SDK preselected
• C.3.1. accept any license agreements
• C.4. click [Finish] and proceed to install the update. When you see feature verification dialog, click [Install].
• C.5. when you complete the installation, you'll be prompted to restart. Select [Yes] to restart the platform
• C.6. workbench should restart automatically
• PLEASE NOTE: at this point you are no longer executing the update manager code you started with, but rather are running a version of the update manager that was contained in the update (along with the rest of the platform plug-ins). Depending on what the update site contained at that point (changes build to build) the platform may not even restart, and you may need to reinstall eclipse to continue. Report defects for this (to make sure there is not actually a legitimate problem) but please be clear that you failed in step C.6.
• C.7. go to Help> About> [Plug-In Details] and [Feature Details] to verify you are running new version of the platform (the versions for the items will be 2.1.0.<qualifier>)
• C.8. Go to Help> Software Updates> Update Manager and expand "Current Configuration" and verify you now recognize the new version of the platform that was updated

D. Restoring Original Configuration

• D.1. in Update Manager, expand "Saved Configurations"
• D.2. select "Baseline" created in step B
• D.3. press [Restore]
• D.4. Restart the workbench when prompted
• D.5. workbench should restart automatically, and open into Update Manager
• D.6. expand "Current Configuration" and verify all configured features are the baseline feature versions (generally 2.1.0)
• D.6.1. click "Show Disabled Features" button in the toolbar of the Configurations view. Observe the updated version as disabled.
• D.7. click the "Show Disabled Features" button in the Configuration view tool bar
• D.8. verify "Current Configuration" shows the features updated in steps D and E as disabled (different icon)
• D.9. go to Help> About dialog, [Plug-In Details] and verify you are in fact running the baseline plug-ins (all 2.0.0, except for the "special cases" like Xerces, Ant, Lucene, Tomcat, etc)
• D.10. shut down the workbench

Part 2: Alphabet Soup

Setup:

• http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/

Description:

• base product is a nested feature, my.alphabet, containing two sub-features with base sets of "letters"
• 3 extension features containing additional "letters" (plug-ins). The features have a dependency relationship as follows:
• "round letters" extension pack requires the base to be installed
• "straight letters" extension pack requires "round letters" extension pack to be installed
• "numbers" extension pack requires both "round letters" extension pack and "straight letters" extension pack to be installed

Steps:

• Install second copy of Eclipse to run these scenarios ... do not use your development copy of Eclipse for this.
• either use the default workspace created by the second Eclipse copy, or specify (-data) a new workspace for these scenarios

O. Completing the install

• O.1. after you have installed baseline eclipse, unzip the Alphabet Soup product features from my.alphabet_1.0.0.zip  into the eclipse/ installation directory. The unzip should overwrite the install.ini file that is packaged with Eclipse (sets the Alphabet Soup feature as the primary feature). The product feature .zips can be found in http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/site/native/
• O.2. start eclipse .... after "Completing the install ..." the platform restarts as "Alphabet Soup" application (own Welcome, About)
• O.3. Click on the "Alphabet Soup" button in the tool bar ... you should have letters A, B, C and E (all 1.0.0) in your bowl.
• O.4. Go to the "Alphabet Soup" menu and verify you can interact with each letter (one action per letter on the menu)
• O.5. Open Help> Software Updates> Update Manager
• O.6. Expand "Current Configuration". Verify "Alphabet Soup 1.0.0" is configured, and it contains 2 sub-features (Round and Straight letters)
• O.7. click on each of the features and view more details about each feature
• O.8. select "Alphabet Soup 1.0.0" and press [Disable]. You should be notified that you cannot disable the primary feature (if this is not the case, [Cancel] the disable action and report a defect).

P. Updating the primary feature using update manager

• P.1. expand "Sites to Visit", and "Alphabet Soup Update Site" and "Alphabet Soup Category"
• P.2. Select "Alphabet Soup 1.0.0" ... preview should not show [Update] button
• P.3. Select "Alphabet Soup 1.0.1" and select [Update]. Go through the install wizard accepting defaults.
• P.4. Restart the workbench when prompted. Will restart with update manager open.
• P.5. Expand "Current Configuration" .... verify you now have Alphabet Soup 1.0.1 installed and configured.
• P.6. Click the "Show disabled features" filter button .... should see both versions (one enabled, the other disabled (icon with red "stop" overlay))
• P.7. click the "Alphabet Soup" tool button ... should show new versions of the base letters (1.0.1). The actions on "Alphabet Soup" menu should also indicate we are running the new version.
• P.8. close update manager
• P.9. shut down the workbench

Q. Updating the primary feature using "native" install (.zip)

• Q.1. unzip the Alphabet Soup product features from my.alphabet_1.1.0.zip  into the eclipse/ installation directory (look into the features/ or plugins/ subdirectory to verify you see new 1.1.0 versions)
• Q.2. start Eclipse (a.k.a. Alphabet Soup). You'll see the splash coming up twice as the platform is updating the configuration. Workbench will come up, with a dialog informing you have changes. Click [OK] to open the update manager change dialog.
• Q.3. check the change (so it is applied) and press [Finish]
• Q.4. restart the workbench when prompted
• Q.5. click the "Alphabet Soup" tool button and trigger "Alphabet Soup" menu action to see you have the new version (1.1.0) of the "soup bowl and letters"
• Q.6. Open update manager and expand "Current Configuration". Should see Alphabet Soup 1.1.0 enabled, and the other 2 disabled (click the "Show disabled features").

R. Adding an extension using the update manager

• R.1. expand "Sites to Visit", "Alphabet Soup Update Site", "Alphabet Soup Fun Pack - Round Letters"
• R.2. select "Alphabet Soup Round Letters Extension Pack 1.0.0" and click [Install]. Accept defaults in wizard and [Finish]. Restart workbench when prompted.
• R.3. click of the "Alphabet Soup" tool button and interact with "Alphabet Soup" menu to see new round letters (D and G). Note: may need to go to Window> Customize Perspective...> Other and select the action sets for the new letters
• R.4. expand Current Configuration and verify the new feature is showing as configured.
• R.5. close the update manager and shut down the workbench
• R.6. As an alternative, try to install several extension features at once using group install. For each feature you want to add, check the checkbox at the bottom of the Preview for that feature. When done, go to 'Selected Updates' view and process all the pending jobs. A multi-install wizard should guide you through the installation.

S. Adding an extension using "native" install (.zip) and link file

• S.0. Note: the first 3 steps will typically be performed by a native installer. Since you are simulating these steps you need to do this manually.
• S.1. Set up a new install directory somewhere in your file system. Create eclipse/ subdirectory under it. Unzip the Alphabet Soup Straight Letters extension  from my.alphabet.more.straight.letters_1.0.0.zip  into the eclipse/ subdirectory. You should end up with
• <some new install directory>/

      eclipse/
            features/
            plugins/
• S.2. In the original eclipse install (the one that contains the platform and Alphabet Soup), create a new directory called "links" as a peer to features/ and plugins/. You should end up with
• <eclipse platform install directory>/

      eclipse/
            links/
           features/
            plugins/
• S.3. within the links/ subdirectory, create a file called my.alphabet.link  and add a single line into it


    path=<some new install directory>

Note: the path should be an absolute path using local file system syntax. The .link file is loaded as a Java properties file, so on Windows you need to double up the back-slashes (e.g. path=c:\\temp\\install)

• S.4. start eclipse (Alphabet Soup). You'll see the splash coming up twice as the platform is updating the configuration. Workbench will come up, with a dialog informing you have changes. Click [OK] to open the update manager change dialog.
• S.5. check the change (so it is applied) and press [Finish]
• S.6. restart the workbench when prompted
• S.7. click the "Alphabet Soup" tool button and trigger "Alphabet Soup" menu action to see you have the new letters.

Note: may need to go to Window> Customize Perspective...> Other and select the new letters to get the menu actions to become visible
Note: if you are following all the steps in the scenario, the base letters (A, B, C, E) should be at 1.1.0, and the extensions (D, G) (F, H) at 1.0.0
• S.8. Open update manager and expand "Current Configuration". Should see a new site representing the extension install, and it should contain the extension feature you've installed.
• S.9. Click on the new extension, and disable it in the Preview view. After restart, verify that all the features and plug-ins from the extension are missing. Enable it and verify that they are back after the restart.

T. Installing another extension using the update manager (with environment filtering)

• T.1. expand "Sites to Visit", "Alphabet Soup Update Site", "Alphabet Soup Fun Pack - Numbers"
• T.2. The Numbers extension specifies an OS in its feature definition. The update site contains features for Win and Linux. On those two platforms you should see a list of features designated for than platform. On other platforms you are out of luck ... you don't get to play with numbers (skip the rest of this step)
• T.3. uncheck the "Show matching features only" filter .... should now see all the features for both platforms. Check the filter back again.
• T.4. select "Alphabet Soup Numbers Extension Pack for <OS>1.0.1" and click [Install]. Accept defaults in wizard. In the location selection page ensure the extension location created in steps S is not offered as a choice. Press [Finish]. Restart workbench when prompted.
• T.5. click of the "Alphabet Soup" tool button and interact with "Alphabet Soup" menu to see new numbers (3 and 5). Note: may need to go to Window> Customize Perspective...> Other and select the action sets for the new numbers
• T.6. expand Current Configuration and verify the new feature is showing as configured in the original install site
• T.7. close the update manager and shut down the workbench

"Free-form" testing

• the above scenarios describe a path through the update support. Run through it once as described. There is lot's of opportunity to do thing in different order, click on ither buttons, try other features in the UI. Go ahead an explore. Remember, is you see something that does not work, is not correct, or is not what you'd expected, open Bugzilla defects in the platform/update component. Please ALWAYS specify the steps leading up to the failure, and include a .zip of the <workspace>/.metadata/ directory

Part 3: Optional features and e-fixes

Setup:

Available sites:

• http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/

The above site contains pre-built features used as part of the following scenario steps.
 

Description:

The Optional Site is a simple site that contains several versions of the 'Root' feature. The feature includes another feature (XYZBogus) that in turn includes features XYZ and Bogus. The last two features are included as optional, which means that users can elect not to install them. Several interesting consequences result from this capability, and this part deals with them.

The site also contains several e-fixes. E-fix is a feature that is designed to patch another feature with an exact ID and version. It is used to deliver temporary fixes between full root updates.

A. Installing feature Root 1.0.0

A1. Open Update Manager. Create a bookmark with the URL listed above.
A2. Expand the new node and select feature Root 1.0.0. Press 'Install' button in the Preview view.
A3. Accept the license in the License page.
A4. Uncheck 'XYZ 1.0.0' optional feature in the Optional Features page. Leave 'Bogus 1.0.0' feature selected.
A5. Install (accept unsigned feature). Restart.
A6. Verify that 'Root 1.0.0' feature has been installed and that 'XYZ 1.0.0' is missing.
A7. Toggle the view button so that disabled features are visible. Verify that 'XYZ 1.0.0' is shown and marked as '(not installed')
A8. If you want to stop being warned about unsigned features, toggle the option off in the Install/Update preferences. Verify that you are warned about the consequences (rogue features deleting your entire hard drive and such).

B. Updating Root 1.0.0 to Root 1.0.1

B1. Open Update Manager. Expand 'Optional site' bookmark created in scenario A and select 'Root 1.0.1'. Verify that Preview view shows 'Update' button. Press it.
B2. After accepting the license, verify that features 'XYZBogus' and 'Bogus' are checked  and grayed out in 'Optional Features' page, while 'XYZ' plug-ins is unchecked (leave it unchecked). Install and restart.
B3. Verify that we now have Root 1.0.1 installed that is still without XYZ feature (XYZ 1.0.1 shows as 'not installed' when disabled features are shown in the view).

C. Preserving the state of the optional feature

C1. Close Eclipse. Manually delete all 'com.example.*' features from the features/ directory and all 'com.example.*' plug-ins from the plugins/ directory. Delete the '.config' directory in the .metadata directory of the workspace (you want to preserve the bookmark).
C2. Repeat scenario A but this time leave all the optional features selected.
C3. Restart and open current configuration. Verify that all the features are showing as enabled.
C4. Select 'XYZ 1.0.0' feature and select 'Disable' button in the preview. Restart.
C5. Verify that 'XYZ 1.0.0' feature is now disabled in the 'Root 1.0.0' hierarchy (you will need to make disabled features visible in the view to do that).
C6. Move to the Updates view and find Root 1.0.1 feature in 'Optional Site' bookmark. Click on 'Update' button.
C7. After accepting the license, leave all settings default and install the new version. Restart.
C8. Verify that 'Root 1.0.1' is now installed, and that 'XYZBogus 1.0.1' and 'Bogus 1.0.1' are showing in the hierarchy. Also verify that 'XYZ 1.0.1' is installed but disabled (we are testing whether the original state of XYZ 1.0.0 was preserved during the update). The expected outcome is that the new version of XYZ is installed but it remains disabled as before.

D1. Installing the missing optional feature (from the originating site)

D1.1. Repeat cleanup as in C1.
D1.2. Repeat the scenario A.
D1.3. After the restart, go back to the Updates view and select Root 1.0.0 again. Verify that the action button is visible and that the label is "Change". Press it.
D1.4. When in 'Optional Features' wizard page, ensure that 'Bogus 1.0.0' optional feature is checked and grayed out. Select 'XYZ 1.0.0' feature. Finish the install. Restart.
D1.5. Verify that we now have all the features in 'Root 1.0.0' hierarchy in the current configuration.

D2. Installing the missing optional feature (using the saved originating site URL)

D2.1. After finishing D1., delete XYZ 1.0.0 feature and XYZ 1.0.0 plug-in manually from features and plugins directories, respectively.
D2.2. After restart, open Update Manager and toggle 'Show Disabled Features' button on the 'Configuration' view. Select 'XYZ 1.0.0' feature object (should be shown as 'not installed').
D2.3. Verify that the 'Install' button is shown in the Details view. Press it.
D2.4. When the install wizard shows up, follow it until XYZ 1.0.0 plug-in is installed. Cool: missing optional feature reference has a preserved URL of the originating site that it can use to reconnect and install it later.

E. Discovering missing optional feature

E1. Manually copy 'com.example.xyz_1.0.0' from 'features' directory and 'com.example.xyz_1.0.0' from 'plugins' directory into a temp. place. After that, repeat cleanup as in C1.
E2. Repeat the scenario A and verify that XYZ 1.0.0 is missing from the configuration (shown as 'not installed').
E3. Close Eclipse. Manually copy 'com.example.xyz_1.0.0' feature from the temp. space into the 'features' directory and 'com.example.xyz_1.0.0' plug-in from the temp. space into the 'plugins' directory. Start Eclipse.
E4. Verify that no dialog was shown and that feature XYZ 1.0.0 was detected and configured into the hierarchy of 'Root 1.0.0'.

F. Installing missing optional features natively after updates

F1. Repeat preservation + cleanup as in E1.
F2. Repeat the scenario A.
F3. Run the 'one-click' update (Help->Software Updates->New Updates). The wizard should discover feature 'Root 1.0.1'. Accept the license and finish install. Restart.
F4. At this point, we should have installed Root 1.0.1 with XYZBogus 1.0.1 and Bogus 1.0.1, but not XYZ 1.0.1 (not installed because we didn't have XYZ 1.0.0 and one-click update should only update installed software).
F5. Manually copy feature XYZ 1.0.0 from the temp space and plug-in XYZ 1.0.0 from the temp space as in E3.
F6. At this point, verify that XYZ 1.0.0 is present in the hierarchy of XYZ 1.0.0 but disabled because Root 1.0.0 is disabled.
F7. Run the 'one-click' update again as in F3. It should discover XYZ 1.0.1 again because we now have previous version of XYZ and it can now bring it up to 1.0.1
F8. Verify in the configuration that XYZ 1.0.1 is now installed and enabled.

Note: as you go through the the scenarios G, H and I that deal with e-fixes, it is recommended to increase the coverage by switching between multiple workspaces (install couple of e-fixes, then start with a new workspace, install some more, create a new workspace, install some more, than switch back to the first one). Since state is stored in each workspace, that will give Update an additional workout to reconcile its state with changes in the file system (both partial and full reconcilers will kick in).

G1. Cumulative patches

G1.1 Repeat steps C1, C2 and C3 to install Root 1.0.0 feature hierarchy. Verify that all Root features (including optional ones) are installed.
G1.2 Expand optional site bookmark in Updates and locate folder "Emergency Fixes". Locate feature EFIX e334 1.0.0. Select it and install it.
G1.3 After restart, verify that EFIX e334 has been installed and that it includes XYZ 1.0.0.e334. The same XYZ feature should be included by Root 1.0.0->XYZ Bogus 1.0.0 (should show up arrow indicating branch update). There should be no errors or warnings.
G1.4 Expand optional site bookmark in Updates and locate folder "Emergency Fixes". Locate feature EFIX e335 1.0.0. Select it and install it. Note: e335 is a cumulative fix because it fixes a problem in XYZ 1.0.0 and also includes a fix in e334.
G1.5 After restart, verify that e335 has been installed and that it includes XYZ 1.0.0.e335. The same XYZ feature should be included by Root 1.0.0->XYZ Bogus 1.0.0 (should show up arrow indicating branch update). 
G1.6 The same XYZ 1.0.0.e335 should also show up as a child of EFIX e334. The interpretation is that XYZ 1.0.0.e335 also includes a fix for e334, so the fact that the previous version has been disabled does not invalidate EFIX e334.

G2. Patches that include other patches

G2.1. Repeat steps C1, C2 and C3 to install Root 1.0.0 feature hierarchy. Verify that all Root features (including optional ones) are installed.
G2.2. Expand optional site bookmark in Updates and locate folder 'Emergency Fixes'. Locate feature EFIX e452 1.0.0. Select it and install it.
G2.3. After restart, verify that: EFIX e452 is installed; its child feature e388 should include Bogus Feature 1.0.0.e388. The same Bogus Feature should be included by Root 1.0.0 hierarchy. There should be no errors or warnings.
G2.4. Expand 'Saved Configurations' folder. Verify that a backup configuration for e452 has been created (backup configurations have label in format "@<id_version>  backup".

H. Updating feature branches with partial patch cleanup

H1. After installing patch e452 in scenario G2, search for new updates by selecting 'Window->Updates->New Updates'.
H2. When the update wizard comes up with the results, uncheck the checkbox 'Filter features included ...'. Uncheck "Root 1.0.1" and check "XYZBogus 1.0.1" from the list of search results. Cool: this demonstrates how branches in the feature hierarchy can be individually updated.
H3. Accept the license agreement and install the feature.
H4. After restart, verify that Root 1.0.0 now includes XYZBogus 1.0.1 (Cool: XYZBogus 1.0.1 image should have an upward pointing arrow overlay indicating that the feature has been updated from the original version specified in the Root 1.0.0 manifest). Also verify that e388 does not show up anywhere, but EFIX e452 should still be present in the configuration.

Note: Technically, since EFIX e452 includes EFIX e388 and since e388 is now disabled because XYZBogus 1.0.1 is updated, EFIX e452 should show error status (missing included feature). Update performs additional computation in this case to find if e452 is really broken. The fact is that even though the referenced feature e388 is disabled, it is a patch for XYZBogus 1.0.0 which has since been upgraded. Updates makes a (daring) assumption that a formal update for a feature includes all the patches published for a previous version of that feature. In this particular case, Update assumes that XYZBogus 1.0.1, being an update to XYZBogus 1.0.0, contains all the fixes registered for XYZBogus 1.0.0, including e388. It concludes that EFIX e452 will indirectly satisfy its need for e388 through XYZBogus 1.0.1 code.

I. Updating feature root with patch cleanup

I1. After updating XYZBogus in scenario H, search for updates again. This time, accept the default (Root 1.0.1) and install it.
I2. After restart, verify that Root 1.0.1 is installed and that all the included features are version 1.0.1. Also verify that there are no e-fixes left enabled in the configuration.
I3. Open file ".install-log" in <workspace>/.metadata/.config/ and verify that it contains logs of all the activities performed in scenarios G, H and I.

J. Handling cross-site version conflicts

The role of this scenario is to show how cross-site conflicts are handled. Cross-site conflicts are caused by root features in separate install sites that include features of the same ID but different versions. Since both features will be configured and their plug-ins contributed to the Eclipse runtime, runtime will resolve the duplication by selecting plug-ins with the higher version. Update warns about this 'silent' upgrade when an attempt is made to install or update a feature that can cause such a conflict to appear.

• Available sites: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/extensionSite/

J1. Repeat cleanup as in C1.
J2. Select "Optional Site" bookmark as in A1 and install Root 1.0.0 with all the optional features. Restart.
J3. Add another bookmark called "Extension Site" with the URL as shown above.
J4. Expand the bookmark object and select feature "Root Extension 1.0.0". Press "Install" button.
J5. Accept the license and select both the optional features for install.
J6. Do not accept the default target install site. Instead, create a new one by pressing "Add" button. Choose a location outside the Eclipse product tree (anywhere else on the disk). Press "Finish". Restart.
J7. Verify that the current configuration has two install sites. The first one should contain Eclipse features and Root 1.0.0. The second one (the one you picked in J6) should contain Root Product Extension 1.0.0. There should be no conflicts.
J8. Search for new updates by selecting "Window->Updates->New Updates". You should get two results: Root 1.0.1 and Root Extension 1.0.1. Uncheck Root 1.0.1. Press "Next" and accept all other default settings until "Finish" is enabled. Press Finish".
J9. Verify that a warning dialog is opened explaining the conflict. The conflict should be caused by XYZ and Bogus features that will be 1.0.0 in one site and 1.0.1 in another if the update proceeds. Answer "No".
J10. Return back to the first page of the wizard and select both results (Root 1.0.1 and Root Extension 1.0.1). Advance to the last page and press "Finish" again. This time, there should be no conflicts because both XYZ and Bogus features will be simultaneously updated to version 1.0.1.
J11. After restart, verify that the current configuration shows no warning overlays.

I. Web-triggered updates

Update Manager has a neat feature whereby it can run a Web application and accept calls from a browser with the right URL. Tasks like presentation, search, classification, user verification etc. can all be handled by the provider's web site (presumably running a Web application itself). Features and plug-ins are still in the standard update sites, but these sites are used as feature servers. When users click on 'Download' or similar buttons or links, a URL query is composed and sent to Eclipse with the Update Web application running. Update servlet receives the query and initiates the install process. At this point, we are in the familiar install wizard.

• Available sites: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/index.html

I1. Repeat the cleanup as in C1.
I2. Open "Preferences" dialog and select "Install/Update->Web-triggered updates" page. Turn the web application on. When pressing "OK" there will be a couple of seconds delay (starting the Tomcat server).
I3. Open Update Manager and create a new site bookmark using the URL listed above. When in the wizard, choose the non-default 'Web site' bookmark type. Finish.
I4. Double-click on the bookmark to cause the External Preview view to open (note: this is only on Windows; on other platform, the page will open in a standalone Web browser).
I5. You should see a page with two Download buttons. Press on the Download button for Root 1.0.0. Verify that a progress monitor dialog opens while connecting to the feature server. Eventually, Install Wizard should show up. Follow it to install Root 1.0.0.
I6. After restart, double-click on the Web link again and click on the 'Download' button for Root 1.0.0. This time, a problem response page should show up indicating that the requested feature is already installed.
I7. Click on the 'Download' button for the feature Root 1.0.1. This one should be treated as an update. Follow it to the end and restart.
I8. Verify that the configuration shows the correct features.