That’s not what I meant. There are other binding with a version range specified (AquaTemp Binding [4.1.0.0;5.0.0.0) for example), where the version range has been “automatically hidden” by some logic before being displayed when you browse it from MainUI. This doesn’t happen for the Mill LAN Binding for some reason I don’t understand. Try to browse the add-ons from MainUI and you will see what I mean.
Edit: I think I get it now. It’s because it’s installed. I uninstalled the Mill LAN Binding, and then the version range isn’t displayed. But, for bindings that are installed, it is. It’s probably not intended to work this way, a small bug in MainUI?
Yes, see my edit. It’s once you install the biding that it becomes “unhidden”. It’s also shown when you press the “+” to add a Thing and get to the “Choose Binding” page in MainUI. I assume it shouldn’t be shown there either.
I find that logic quite peculiar, but that’s another matter. As I understand it, if you use e.g 5.0.0) as the upper bound, it will “match” pre-releases of 5.0.0 but not 5.0.0 itself. Using 5.0.0.0) as the upper bound will make it not match anything 5.x.x as I understand it. I would say that since this logic in entirely defined by OH, I would be smart to change it into something more intuitive.
Regardless, as I see it, the upper bound is usually just a wild guess. In most cases there won’t be a reason why anything would stop working in a future version, and until some breaking change that will make it stop working is known, the end should be open ended. That way things won’t “dissapear” from the Marketplace if the author doesn’t “keep up” and keep bumping the upper bound. I’ve thus made this suggestion, which would allow open-ended ranges like [4.1.0;): https://github.com/openhab/openhab-core/issues/4523
