| [platform-update-dev] Cannot uninstall a feature? |
I'm enabling Update Manager support in our PalmSource Eclipse based product and ran into something strange. Here's the setup on Eclipse 3.0.1:
I have features A and B. There are unrelated (no dependencies between them). Feature A is a product feature (aka primary feature), B is not. If I start eclipse the first time (i.e. no data in the configuration directory except config.ini), both features are enabled when I look at the Manage Configuration dialog. But to my surprise, I can disable B but cannot uninstall feature B (selection grayed out/not present). I would have thought that as long as it's not the primary feature and has no other features depending on it, I could uninstall it.
More testing: I start the product for the first time with only feature A (the product feature) . I then later install Feature B through the Update Manager and restart. As expected, A and B are enabled. When I look at the Manage Configuration dialog, I see that I can disable B as well as uninstall B. This is as I would expect. So it seems that if B is present at first startup, then it cannot be uninstalled at any time later.
To confirm that hypothesis, I then closed the eclipse instance, deleted the contents of the configuration directory (except config.ini) and restarted to simulate a "first-time" start. Both A and B were enabled, and I could not uninstall B, just like the first scenario I described.
Is this intended? What's the reason for it? Is there anything I can do about it in config.ini, B's feature.xml, or any other configuration/metadata file?
Thanks!
Brad