Re: [platform-update-dev] Re: Launching branded products based on Workbe

["Pat McCarthy" <patmc@xxxxxxxxxx>]

Ok, that helps.   But of course... some questions back:

You said:
> * the location of the workspace does not matter .... you can set it up
> anywhere and specify -data <path> on launch, or you can let it default
> (which would not work if the product is installed in r/o space). There is

> no need to place the .exe in the workspace directory

In the last phrase - '.exe in the workspace directory' - do you mean .exe
in the Workbench directory?

Also - in reading the spec from 11/22/01 - there is a bit about where this
config info is stored:
> Eclipse Startup Processing

> Eclipse runtime instances execute from a shared program installation. The
startup
> configuration for each runtime instance is maintained as metadata in the
platform user area
> (the "root" directory structure used > to hold other Eclipse runtime
files, and the
> Eclipse workbench resources). The information is used at startup time as
a quick means
> for detecting "material" changes to the Eclipse installation, and to
compute the set
> of plug-ins (ie. the plug-in path) to be used for the Eclipse platform
execution. The
> configuration information is maintained by the installation and update
support.

If config info is stored in the workspace how will this impact people that
use the workbench against multiple different workspaces (different
roles/major projects).


Pat McCarthy   --   Eclipse Platform Enablement (3ECA)
                             --   OTI - RTP, NC
                             --   (919 254-6231 / 8-444-6231 -- FAX
8-444-4183)
                             --   Internet: PatMc@xxxxxxxxxx

                             --   Lotus: Pat McCarthy/Raleigh/IBM