Community
Participate
Working Groups
Eclipse has advanced quite quickly with new use-cases (RCP, Equinox, server side, etc.) and new technologies (e.g., OSGi and OSGi's MEG) coming into the picture. To date Update Manager has not been enhanced to support or exploit these changes. In 3.3 we will investigate provisioning support for enhanced workflows, the ability to update the so-called "root files" (e.g., startup.jar, eclipse.exe), improved efficiency (download and disk footprint), support for right-grained discovery and acquisition of function as well as integration with differing repository types. This effort also includes enhancements to the tooling around provisioning.
Comments from an RCP perspective. I only managed to find one example of including the Eclipse update command which now has depreacted methods (since 3.2) and I can't find an uptodate one and don't know enought about bundle version to work it out. So some snippets would be really useful. Updating an RCP application (and removal of unwanted versions) should be easy. I really want an api call like Update.downloadAndInstallUpdatesOnShutdown(URL placeToGoAndLook, boolean removeOlderVersion). This would start a background job to check the url for updates. Download them in the background and then install them when eclipse shuts down so next time it starts up the new version is installed and running. At the moment it is assumed that the RCP users has brains and knows what an update is all about and wants features and all that stuff. We deal with sales people (!) I (an many others from this news forum) do not want to present an update UI to our users (They can barely cope with the UI of the application itself). If I am planning quarterly updates (monthly for the testers) over a 5 year life cycle I don't want the previous 19 versions of code sitting on a users machine. At 5 Mb an update this is getting just a bit extreme. Yes Mr customer I know I am using up 100Mb of your disc space with no good reason. So removal of the previous version(s) of the plugin will be needed.
(In reply to comment #1) Our Client-Server RCP applications need the download and install mechanism before startup, so that the clients never startup against an incompatible server version.
I have started a wiki page listing the requirements for a new / improved provisioning story. See http://wiki.eclipse.org/index.php/Requirements_for_a_new_update_manager
Should we edit the wiki or provide comments here for you to incorporate or not as you see fit.
Let's keep the discussion on the wiki.
*** Bug 146582 has been marked as a duplicate of this bug. ***
*** Bug 123162 has been marked as a duplicate of this bug. ***
Any update on this item? Pun intended ;-)
> Any update on this item? A new work area has been proposed in the Equinox incubator to work on this plan item: http://eclipse.org/equinox/incubator/provisioning/proposal.php.
Marking as dup of 3.4 plan item. *** This bug has been marked as a duplicate of bug 200089 ***
