it's basically a cheap version of dependency locki...
# gradle
o
it's basically a cheap version of dependency locking
g
How is exclude related to dependency locking?
o
allows you to exclude versions you don't want, forcing gradle to pick the one that's left
g
But this is not locking and even not related to versions directly, rather removing some parts of dependencies graph
Gradle has configuration control which allow you to force version of particular dependency and real dependency locking, don't think that exclusion can be called "dependency locking", because locks nothing
o
it isn't dependency locking, but it can be used to emulate it poorly
g
I just think it's misleading statement because you cannot "lock" anything using exclude, just exclude and let Gradle resolve dependencies graph without this dependency If you want to lock some version you have to use resolution strategy API or lock files