[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [platform-update-dev] Difference between InstallRegistry and platform.xml


Chris,

platform.xml is maintained by the update.configurator plugin. This plugin runs early in the eclipse startup, finding what plugins need to be installed, and calls osgi to install those plugins (bundles). At this point the install registry takes over.
So, the install registry has the last word in what is actually running. If you think this is confusing, I won't dispute it :-)

-Dorian



Chris Aniszczyk <zx@xxxxxxxxxx>
Sent by: platform-update-dev-bounces@xxxxxxxxxxx

01/19/2007 02:29 PM

Please respond to
"Eclipse Platform Update component developers list."        <platform-update-dev@xxxxxxxxxxx>

To
platform-update-dev@xxxxxxxxxxx
cc
Subject
[platform-update-dev] Difference between InstallRegistry and        platform.xml





Can someone clarify the difference between the InstallRegistry versus the platform.xml? I understand that the platform.xml is a reflect of what is currently enabled in the platform, but not sure how the InstallRegistry relates, especially in terms of enable/install/disable/uninstall operations. I ran into a case where I had feature org.eclipse.test_1.0.0 in the platform.xml (but it wasn't in the installregistry), went to do an upgrade of that feature and noticed that it didn't disable the older feature but properly enabled the newer feature (ie., updated the platform.xml).

Any wisdom out there?

Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | +1 860 839 2465
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-update-dev