The latest revision strategy is incompatible with OSGi's versioning scheme. For example 1.1.1 is considered to be after 1.1.1.foo. This is at odds with OSGi's versioning rules, and can cause the incorrect revision to be selected when working with bundles from Spring Source's repository (http://www.springsource.com/repository/app/), for example.
Alex Radeski raised this issue about 2 years ago and provided the attached patch to correct it. I propose that we either accept his patch to improve the behavior or follow Xavier Hanin's suggestion and adapt it to provide a separate osgi revision strategy.
For the original discussion of the issue, see this discussion thread: