Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/743
very good spot on `BundleFinder` @geomacy - have cleaned it up so instead
of sorting by version (and _ignoring_ bundle _names_ altogether!) it now sorts
alphanumerically on name, then on version, and in the code where we `findOne`
we take the highest version of the first entry.
as for OSGi ranges that may be a bit of a headache, or at least potentially
a surprise to OSGi users. _however_ so long as we can make it follow our
scheme it should be fine: i would think anyone using a combination of
qualified and unqualified versions would expect semver semantics where
unqualified is last. in osgi people using qualifiers presumably _always_ do
so, and are used to using a datestamp or something similar to ensure ordering
is correct and it will almost certainly still be correct. (IE I don't imagine
anyone would intentionally use `1.0.0.M9` then `1.0.0.M10`, or `1.0.0.M1` then
`1.0.0` and want OSGi semantics to apply!)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
