Open mickaelistria opened 4 years ago
I don't know, I assumed this was normal operation by p2 when bundles are updated in a read-only installation.
Users of the GA versions from Flathub almost never see this dialog because they only get updates every few months.
What is the actual trigger for the migration dialog?
Actually, the artifacts are reused locally, so this doesn't consume bandwidth, only time.
I am not sure if this is Flatpak related.
This issue is specific to the Flatpak packaging of Eclipse IDE. Non-flatpak delivery don't have this issue. I think it's most likely caused by some configuration/state file being lost upon restart with Flatpak.
Might be related to https://github.com/flathub/org.eclipse.Java/issues/12 then.
Can you test if https://github.com/flathub/org.eclipse.Java/pull/90 helps?
I'm using Flatpak for nightlies and try to update often to see latest changes in action. Ideally, I update daily. However, whenever I update, then the migration wizard shows up and I have to reinstall (including re-downloading) everything I already installed. That consumes bandwidth, delays my "time to usability", requires an extra restart... Could this story be somehow improved?