You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until release 2.11.0, it was possible to upgrade the current parent version (in this example 1.58.5-SNAPSHOT) to a fixed SNAPSHOT version which is not necessarily the latest SNAPSHOT (in this example 1.58.6-SNAPSHOT) via:
Since release 2.12.0 (which contains #665 ), this is not possible anymore:
mvn -U -DallowSnapshots=true -DparentVersion=[1.58.6-SNAPSHOT] versions:update-parent
...
[INFO] --- versions-maven-plugin:2.12.0:update-parent (default-cli) @ my-project ---
...
[WARNING] Not updating version: could not resolve any versions
This is still a valid use case and should work as before.
The reason is, that UpdateParentMojo now calls the findLatestVersion method with parameter allowingSnapshots=false instead of null (as it was before) which leads to ignoring the allowSnapshots CLI property inside the findLatestVersion method of AbstractVersionsUpdaterMojo.
Probably providing null for allowingSnapshots method parameter was correct.
The text was updated successfully, but these errors were encountered:
Until release
2.11.0
, it was possible to upgrade the current parent version (in this example1.58.5-SNAPSHOT
) to a fixedSNAPSHOT
version which is not necessarily the latestSNAPSHOT
(in this example1.58.6-SNAPSHOT
) via:Since release
2.12.0
(which contains #665 ), this is not possible anymore:This is still a valid use case and should work as before.
The reason is, that UpdateParentMojo now calls the
findLatestVersion
method with parameterallowingSnapshots=false
instead ofnull
(as it was before) which leads to ignoring theallowSnapshots
CLI property inside thefindLatestVersion
method ofAbstractVersionsUpdaterMojo
.Probably providing
null
forallowingSnapshots
method parameter was correct.The text was updated successfully, but these errors were encountered: