Currently, when using Gradle Daemon, it is possible that dependency versions loaded in previous builds are preserved in future ones.
This is due to the static Map used as a cache in loading files - according to some discussions in the Gradle forums, the daemon intentionally keeps classloaders, and therefore the value of static variables, around.
This behavior is inconsistent for consumers - DependencyConstraints should either drop caching, or use a method which accounts for possible changes to the loaded file (such as an updated date or checksum methodology, in addition to path)
romeara
commented
4 years ago
Currently, when using Gradle Daemon, it is possible that dependency versions loaded in previous builds are preserved in future ones.
This is due to the static Map used as a cache in loading files - according to some discussions in the Gradle forums, the daemon intentionally keeps classloaders, and therefore the value of static variables, around.
This behavior is inconsistent for consumers - DependencyConstraints should either drop caching, or use a method which accounts for possible changes to the loaded file (such as an updated date or checksum methodology, in addition to path)