Community
Participate
Working Groups
Build Identifier: 20100218-1602 Eclipse's p2 check for updates doesn't find mylyn 3.3 update. I'm using Eclipse Java package 3.5.2 (SR2) Reproducible: Always Steps to Reproduce: 1. Install a clean Eclipse 3.5.2 (Java package for example) 2. Press Check for Updates under help. 3. It will say no update is available even though an update for Mylyn 3.3 does exist (Eclipse 3.5.2 seeems to include 3.2.3)
This is probably because the mylyn update site is enabled as part of the package you are installing or because mylyn decided to make their update available on another site than the original one.
The update check only takes root IUs into account. In this case the only root IU is the Java package feature which means the newer Mylyn version will not be found unless a newer version of the Java package is also available. I can see how this can be confusing but it is the the intended behavior.
Reconsider? When a user presses "check for updates" he expects it to check for updates, not only check if a major Eclipse package was released. If you don't want to change this behavior, then the least you can do is make a minor revision to the root IU when a plugin update is available to make check for updates find it.
Markus, do you have any thoughts on that or a reference to the original discussion when the package structure was defined?
Also happens with the mylyn 3.4 update. Seriously, something should be done about this. from a users prespective what's the point in a check for updates button if it doesn't find updates?
I'm making this a feature requests and moving this to p2. The simple solution would be to offer a check for updates that is not limited to root IUs but considers all installed features.
Pascal, Do you think it would be in contradiction with Bug 259537?
*** Bug 394477 has been marked as a duplicate of this bug. ***
*** Bug 402554 has been marked as a duplicate of this bug. ***
