| Summary: | [plan item] Improve update manager search | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dorian Birsan <birsan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | amanji, danjou, danrubel, manahan |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | 3.0 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jim des Rivieres
As part of the refactoring effort, search has been pushed into Update Core. Search APIs have been created (FYI only - APIs can change any time). Automatic update search specification draft is now available Update home page: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update- home/doc/working/scheduler/scheduler.html The automatic search proposal deals with two phases of a feature install: searching and downloading. The user is then prompted for continuing to the installation phase, which actually has two parts: copying features/plugins to the appropriate location and then configuring/unconfiguring some features. Is there a reason not to automate the entire process? Unlike downloading, copying and configuring is a sensitive process that require users to: 1) Make some choices (accept license, optional features etc.) 2) Stop working because any crash caused by the user doing unrelated work in Eclipse may leave Update half-way into copying stuff, resulting in unusable product. Unless there is a really strong demand for it, I would avoid performing the installation phase in the background for now. For those interested, the M2 builds will have a first iteration on automatic updates. You need to enable it on the install preference page (Window->Install->Automatic updates) The automatic updates should be working fine in M3, so I will mark this as fixed. a a |