Bug 106169

Description Pascal Rapicault 2005-08-05 11:18:31 EDT

We need to explore how we can support scenarios where the set of bundles being
run is constrained by the user running eclipse. More generally it means changing
configuration since it can stores user specific informations.

The current solution consists in staging the startup of eclipse: start osgi,
identify the user, and depending on that uninstall and install all the bundles
from the framework. This has the advantage of not requiring any code change in
the code base, however it forces the runtime to reparse all the plugin.xml when
the user has changed from the previous run, and the configuration settings (like
preferences) are shared across users.

Another solution consists in restarting the framework once the user has been
identified. This would require code change in osgi to be able to restart the fwk
without changing the vm.

Yet another solution: store the fwk state into two files. One contains the set
of bundles that are on the osgi.bundles list, the second contains all the other
bundles. The first file is common for all users and basically list all the
bundles required to identify the user. On startup, the framework starts loading
the first file, ask for user identity, change the config area and keep reading
from the secondary file to keep running the fwk.