Impossible to restrict Major version number update - `allowMajorUpdates=false` is not respected about versions HOT 4 CLOSED

Would that mean allowMinorrUpdates is not respected either?

from versions.

@DiJu519, I guess it would.

I added new section "UPDATE: More tests" into issue main body. It thoroughly addresses your question. Look at the case "incremental=true: FAILURE" where property allowMinorUpdates is set to false while there are still changes in minor version number.

In fact, the way this plugin works breaks any assumptions. This makes me wonder if I even understand intentions of all these properties (or anyone uses its functionality at all).

from versions.

I did some testing on this as well with a repo with non-textual semantic versions (ie, no RC, BETA, ALPHA stuff), only numeric triples (xx.yy.zz) with some SNAPSHOTS and got good results, except if the upper bound was equivalent with a -SNAPSHOT. Since I think it is a bit different bug, I logged a separate issue #22

from versions.

@khmarbaise this may need to be re-opened

This same issue is present in the UseLatestSnapshots Goal.

Seems d214f34 fixed all but that goal.

Hitting it now locally

[DEBUG]   (f) allowIncrementalUpdates = true
[DEBUG]   (f) allowMajorUpdates = false
[DEBUG]   (f) allowMinorUpdates = false
[DEBUG]   (f) allowSnapshots = false
[DEBUG]   (f) excludeReactor = true
[DEBUG]   (f) generateBackupPoms = false
[DEBUG]   (f) includesList = 
[DEBUG]   (f) localRepository =       id: local
      url: file:///home/jdileonardo/.m2/repository/
   layout: default
snapshots: [enabled => true, update => always]
 releases: [enabled => true, update => always]

[DEBUG] Looking for latest snapshot of A.B.C:D.E:jar:2.40.6

[INFO] Upper bound: 2.41.0
[DEBUG] Candidate versions [2.40.7-SNAPSHOT, 2.41.0-SNAPSHOT]
[INFO] Updated A.B.C:D.E:jar:2.40.6 to version 2.41.0-SNAPSHOT

from versions.