andrzejj0

Sorry. This is indeed a bug. I must have overlooked this paragraph: > It looks like -DallowMajorUpdates=false allows the latest release older than (X+1).0, and based on Maven version math...

You tried that with `-DallowMajorUpdates=false`? Then it indeed looks like the issue is fixed, since it's not proposing a qualified version of release 4. I think your changes might have...

Still not working on the master branch: ``` mvn org.codehaus.mojo:versions-maven-plugin:2.12.1-SNAPSHOT:display-dependency-updates -DallowMajorUpdates=false ... org.apache.maven.reporting:maven-reporting-impl .... 3.2.0 -> 4.0.0-M2 ```

This ? : operator looks correct to me. Only if allowAny is false can we descend further and look for the unchanged segment. If it's true then we're returning empty()....

Hmm the point the OP is making here is that the ranges for version discovery are incorrect. In particular, upper bound is constructed so that its (segment-1) segment is incremented,...

Hmm I saw that these are your changes. Actually, qualifiers are not restricted to ```java private static final String[] QUALIFIERS = { "snapshot", "alpha", "beta", "milestone", "preview", "rc", "", "sp"...

So, instead of incrementing the next segment to create a bound, which makes you want to exclude those "qualifiers", I'm actually thinking of introducing a notion of infinity on a...

> infinity or ^ will need change maven itself Noo, it's not that hard. It's the version comparator which needs to be aware of it, and it's a part of...

Ah, actually I've been looking at it. 😄

Tbh, the function computing the update scope should probably look like this (but, like I said, the scope representation should probably be (internally at least) changed to an enum): ```java...