Invalid version resolved for 1.+ when dependency locking is enabled
#6337
Comments
bigdaz
added a commit
that referenced
this issue
Aug 11, 2018
A bug was causing a selector like `1.+` to select _any_ version when dependency locking was enabled. This change fixes this so that only versions that match the selector will be chosen. Fixes #6337
bigdaz
added a commit
that referenced
this issue
Aug 11, 2018
A bug was causing a selector like `1.+` to select _any_ version when dependency locking was enabled. This change fixes this so that only versions that match the selector will be chosen. Fixes #6337
OdysseusLives
added a commit
to nebula-plugins/gradle-nebula-integration
that referenced
this issue
Aug 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a dependency locking is enabled for a project, dependency versions defined with
N.+are resolved as per+when the lock file is updated.Expected Behavior
Dependency locking is enabled and Gradle is executed with
--write-locks, then a version selector like1.+is resolved in the same way as when dependency locking is not enabled. Given available versions[1.0, 1.1, 2.0],1.+should resolve to1.1.Current Behavior
Version selectors like
1.+are resolve as per+when dependency locking is enabled. Given available versions[1.0, 1.1, 2.0],1.+will resolve to2.0.The text was updated successfully, but these errors were encountered: