Community
Participate
Working Groups
Eclipse 3.3M3: If I "Search for new features" I get different results than if I "Search for updates". To reproduce, I have the update site "Mylar for 3.3" configured to be http://download.eclipse.org/technology/mylar/update-site/e3.3 . I used update manager a few weeks ago to install version 0.9.1 of mylar.bugzilla_feature, mylar.ide_feature, and mylar_feature. This morning I got a notice that a new version was available - did I want to install? I said no because I'd had problems with this in the past and I wanted to do it manually. So I selected Help > Software Updates > Find and Install > Search for updates. The Search Results dialog opened and showed: Mylar for Eclipse 3.3 Features Mylar Task List (Required) 0.9.2 It looked like something was missing so I canceled this dialog and instead selected Help > Software Updates > Find and Install > Search for new features. I selected the "Mylar for 3.3" site, and clicked Finish. Now the Search Results dialog opened and showed: Mylar for Eclipse 3.3 Features Mylar Task List (Required) 0.9.2 Mylar Focused UI (Recommended) 0.9.2 Integration Mylar Connector: Bugzilla 0.9.2 ...etc... (Jira, Trac, Jira core, etc.) Closing this and selecting Help > About, and clicking on the Mylar feature button shows the three Mylar features installed at the 0.9.1 version level. Plug-in details show 14 mylar plug-ins installed, all at the 0.9.1 level. There are no errors currently in the Eclipse error log view. The bug is that all 3 features have updates, but the Find Updates command only says one of them does. I had the same problem with the last upgrade. If I install only the one feature found by Find Updates then Mylar will not work. If it matters, I have Mylar.link in my links directory, pointing to an extension location just for Mylar. I had cleaned out that location right before doing the last upgrade (to 0.9.1).
This is a really bad update manager problem--the update manager does not obey feature dependencies (bug 132450) and causes installs to break for all the users who simply click through the updates. It has been around for ages, several of our users have voted for it, and I have complained about it many times but there has not even been a comment on that bug report. Also see this message to cross-project-issues-dev: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg00381.html What we not found any work-arounds for this, and as as such have always had to document the fact that "Search for updates" should NEVER be used on our download page, in addition to the FAQ (e.g. http://www.eclipse.org/mylar/dl.php ). It doesn't matter, people will still use this and will end up with broken installs. And unless we are doing something wrong (I can't see how, since "Search for new features" always does the right thing) the same breaks should happen for other Europa projects that update their features and rely on the update manager.
Should it be a dup of 132450 then?
(In reply to comment #2) > Should it be a dup of 132450 then? > I think so. I'm guessing that the problem is personnel. And that nobody wants to touch UM code with a 10-foot pole this close to M5 feature/API freeze.
Marking as duplicate since it is one, and since I'm desperately trying to bring attention to that bug. *** This bug has been marked as a duplicate of bug 132450 ***
