If you try to update eclipse or any eclipse based product (f.e. RAD) and it takes 2 hours to display first update window... you probably are in a big company, behind the proxy, and with local DNS servers that do not know anything about internet.
Please call your network administrator and tell him to configure DNS to answer server failed, and not to pretend to not exist... cause Update Manager contacts eclipse update sites *before* displaying the first update window... and it does it a lot of times. Default timeout for DNS query is about half a minute...
And now good news: new update manager will be shipped with Eclipse 3.4 (next summer).
Cheers!
Subscribe to:
Post Comments (Atom)
4 comments:
The mention of an improved update manager made me look it up. I have to say I'm disappointed. I was hoping for something along the lines of Monodevelop's Add-In Manager, ie a simpler take on adding and managing plugins at a high level rather than exposing all the dirty details.
The work out of provisioning currently isn't product ready and will go under many revisions as far as I know.
Fair dues. My concern is that Eclipse will provide a complex provisioning framework UI, leaving the "70% solution" to aftermarket integrators.
Todd
The legacy Update code is currently in the 'critical fix only' mode to allow the Provisioning team to fully focus on the better solution. We are not simply ignoring the woes of the Update users - we are realizing that a full rewrite would be a better strategic solution than an incremental update (pardon my pun :-).
Post a Comment