Screenshots of mentioned problem were attached

Looks like there is reference to different update site with Spring IDE 2.7.2 and p2 pickups latest one

Cannot reproduce. When I take jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201110221347R-H39-M4 and install Spring IDE (JBDS feature 1.1.0, containing Springsource's Spring IDE 2.6.0) from the extras site (http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M4_extras/) I only get 2.6.0 installed:

Did you have the 2.7.2 site [1] in your list of avail sites too, because you were testing JBDS-1863?

[1] http://download.jboss.org/jbosstools/updates/requirements/springide/2.7.2.201109122348/

If so, then yes, JBDS would have searched all available sites and installed for you the latest it could find.

You can uninstall 2.7.2 and 2.6.0, then disable that URL (or remove it from JBDS entirely) and try again. Or try again from a clean JBDS install. Suspect you'll find all's well here.

Install from extra update site for 5.0.0.M4 is fine as soon as there is no external update site is added that leads to latest Spring IDE. It means our extra update feature has open version ranges for Spring IDE.

Are you saying we shouldn't allow users to manually update to a newer (unsupported) SpringIDE version that what we provide OOTB? Cuz... not sure I agree w/ that.

Nope, I'm saying if user selects to install Spring IDE (certified) it must get certified version not something else from external update site. If user wants different version (later then certified), then he has to add an update site and and install from it. If he has certified version installed it wouldn't let him install other Spring IDE until certified feature is removed.

It was really case of including 2.7.2 update-site. It was in time, I thought this update-site was broken (Nick knows, what I am talking about) so I thought this site had no contribution to list of features/plugins to be installed. Marked as Resolved - Rejected.