Scenario: Updating Eclipse Install Using The Update Manager

Last Updated: June 11, 2002 6:05PM

Objectives:

The objective of these scenarios is to illustrate the Eclipse update manager function through simple end-to-end use cases. The scenarios are divided into two parts.

Part 1: Updating Eclipse - "One Click" Update

Setup:

Available sites:
*** PLEASE READ *** PLEASE READ *** PLEASE READ *** PLEASE READ ***
As part of this scenario you will be downloading and installing various versions of the Eclipse components into the running Eclipse. The update site is populated with features that have their version numbers modified as part of the build process. They are generally of the form 2.0.0.QUALIFIER, where the qualifier differs build to build. Note, however, that when you install base Eclipse (.zip downloaded from eclipse.org), all of its features and plugins only use 3 part version identifiers (generally 2.0.0). So all the 2.0.0.Q updates in fact appear more recent that the build you are running, even though they may in fact be an older build. Note, that when you update the Eclipse components from the update site and restart you may in fact now be running DIFFERENT CODE THAN WHAT YOU STARTED WITH. So it is really important that you start each of the test scenario steps with a clean install of eclipse. It is suggested that you always use a second install of Eclipse running with a different workspace (than what you use to do development) to actually run through these scenarios.

When openning Bugzilla defects, use the platform/update component. Please ALWAYS specify the failing scenario step, and include a .zip of the <workspace>/.metadata/ directory

Steps:

A. Startup new Eclipse

B. Save baseline configuration

C. "One Click" update

D. Restoring Original Configuration

Part 2: Alphabet Soup

Setup:

Available sites: The above site contains prebuilt features used as part of the following scenario steps. It also includes several .zip files (containing features and plugins) that are used to simulate native installer steps.
 
*** PLEASE READ *** PLEASE READ *** PLEASE READ *** PLEASE READ ***
When openning Bugzilla defects, use the platform/update component. Please ALWAYS specify the failing scenario step, and include a .zip of the <workspace>/.metadata/ directory

Description:

The Alphabet Soup is a simple application packaged as an Eclipse product, plus several extensions. The application installs a tool button, and a menu ("Alphabet Soup") that can be used to query the content of the "soup bowl" and interact with the individual installed "letters" (each letter in the bowl corresponds to a separate plugin) Just follow the steps and you'll get the idea.

Steps:

O. Completing the install

P. Updating the primary feature using update manager

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

R. Adding an extension using the update manager

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

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

"Free-form" testing