Community
Participate
Working Groups
There's several other bugs open about how Update Manager should be able to "recover" (in some form) from errors received while retrieving files. For example, if a mirror is "temporarily unavailable" or a "file not found" then Update Manager could (as suggested solutions) "retry" at users choice, or, preferably, simply go back to the "home" server to attempt to satisfy the request. There's another "error" condition though that has not been captured in a "recover" bug. That is the type of error seen in bug 149366. There are some common configurations of servers that will return HTML instead of a binary jar, seen so far for jars with "map" in their name. In these cases, Update Manager can, I believe, see from the HTTP header that its getting HTML instead of a Jar, and even though response code would be "ok", it should fall back and get the jar from another server (presumably, the "home" server).
I'd prefer if the update code would allow to specify two or three update mirrors to try before it should go to the home site. Some way to gather these errors (so they can be fixed quickly) would be nice (like permission denied, etc). If the update code would "call home" with the health of the mirrors, that would help to improve the situation. I'm a bit unsure about the "legal" side of this, though that is how users will like the idea :-/
The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2.
