Re: [platform-update-dev] Shared vs. per-user configuration consistency

[Dorian Birsan <birsan@xxxxxxxxxx>]

Brian,

What kind of errors are you getting?
The update startup code has two main
paths: it works with cached plugin data is possible, or it tries to reconcile
what it finds on the installation location(s) with what the OSGi runtime
is configured with. Cached plugins are used when nothing changes. In your
scenario, when the product is removed, the update should detect that when
checking the runtime platform timestamp (I assume that the platform returns
the correct timestamp when you remove/re-install the product). In that
case, all the plugins should be re-installed in the osgi runtime. 
You may want to open a bug report on
either Platform Runtime or Update.

-Dorian

Brian Eliot <beliot@xxxxxxxxxx>
Sent by: platform-update-dev-admin@xxxxxxxxxxx

01/28/2005 10:03 PM

Please respond to
platform-update-dev

To	platform-update-dev@xxxxxxxxxxx
cc
Subject	[platform-update-dev] Shared vs. per-user configuration consistency

When a per-user configuration is created (e.g., in
$HOME/.eclipse)
it is linked to the shared configuration in the product install
location.  If the shared configuration is subsequently invalidated,
say through a product removal/re-install cycle, the per-user
configuration appears to remain intact, generally resulting in
runtime exceptions when launching the workbench as that user, until
the per-user configuration is forcibly removed (either the entire
configuration/ directory or at least platform.xml).  It would be
difficult for an installer to find and invalidate all these
separate configurations when replacing the product.

Is there any detection that the shared configuration link from
config.ini is out of date, and if not, is there a clean way to
force the per-user configuration to be refreshed?  Neither the
-initialize or -clean options appear to have any effect.  The
working assumption is that if the product install location has
been completely recreated, any preexisting feature configuration
for this user is automatically invalid and does not need to be
preserved.
---
Brian Eliot
MontaVista Software, Inc.
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev