|[equinox-dev] testing status/UI status so far...|
I've spent most of today finding a bug, finding that someone already reported it, investigating the big ones a bit, etc.
My take for M4 is that there are at least a couple of code paths that are causing some bad things to happen in the profile. I've tried to investigate enough to determine that the UI is not hiding the problems by ignoring exceptions or failure statuses.
In particular, I'm seeing:
Profile can get blown away (it is in the registry but has no content) if you try to update with more than one version of an IU selected in the update wizard.
This problem is exacerbated by two related bugs:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212295 - here, the UI is showing all available updates for an IU vs. just picking the latest one
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212609 - here, the planner is saying that there are updates available for an IU even when the "updates" are older
There are times when the profile's contents remain in tact, as far as the provisioned SDK still being usable, but the user UI doesn't know that anything is installed.
There are other annoying UI issues (disappearing restart dialogs, hanging wizards) that seem to happen in error cases or during cancellation, but when I do the mainstream/non-failing use cases, I don't observe these problems.
I could investigate a temp fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=212295 if we feel like the underlying issues cannot be solved and we want to try to prevent the fail cases.
The rest of the UI problems I would rather fix in the context of some wizard/auto update code reorg that will take a day or two, unless someone raises the severity...