Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] A "releases/latest" URL in the IDE to ease upgrades?

Auto-update to latest releases, definitely. It always baffled me why this wasn't the case in the first place.

For users that have 3rd party plugins in their Eclipse installation (plugins that are not included in the standard Eclipse distros), downloading a new Eclipse distro is too annoying, because then you have to install all the 3rd party plugins again. So you end up having to add the new major release update site, manually, everytime, to then update. And for Eclipse newbies, this is not an obvious thing at all!

If 3rd party plugins properly do dependency version management, this shouldn't be a problem.

On Thu, Dec 3, 2015 at 2:44 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Today I had to assist a user in upgrading from Luna to Mars. He didn't do it so far because he was a bit lazy to re-download a package and re-install all his favorite bundles. I told him about the upgrade, ant the first thing he tried was "Check for updates", that didn't work. Then he had to look for help on Google to do the upgrade. He reached a StackOverfow post that was not very positive about Eclipse IDE, but that drive him to the solution of adding and enabling the releases/mars URL and then trying Check for Updates successfully.
IMO, there is one lesson to learn from this user story: some users expect "Check for updates" to provide updates.
I believe in order to provide that, it's mainly a matter of creating a releases/latest URL that would reference the latest release and be updated whenever necessary, and to enable this URL in Eclipse EPP packages by default.
Now the question is more: "Is this something we want to do?". For the plain Eclipse IDE user, I believe it would be profitable since updates would be more accessible. The doubt remains on the plugin providers: in case they don't have their content ready for the next release when it happens, then it means that user can reach a worse state when they update, because of those 3rd-party plugins. However, good management of dependency versions should be able to spot that and at least show an error (with remediation) when trying to update.

What do you think it best: auto-update to new major, or expect users to do the steps mentioned above to adopt the latest improvements?
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

ide-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top