It's a plugin - palantir-consistent-versions. I haven't used the built-in
gradle mechanism, so I can't
say much about how it works.
D.
On Mon, Feb 22, 2021 at 10:45 PM David Smiley wrote:
> I noticed that Gradle has a built-in dependency version locking mechanism
> that is different than the
Thanks for the background on that. I suspected it was a new feature.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Feb 22, 2021 at 5:02 PM Mike Drob wrote:
> This feature was added to Gradle 6.2, which wasn't available when we first
> did
This feature was added to Gradle 6.2, which wasn't available when we first
did the conversion from ant.
This plugin doesn't do any verification of license and notice files like we
do, so that's one thing that we will still need our custom validation for.
We could potentially move the checksum
I noticed that Gradle has a built-in dependency version locking mechanism
that is different than the one we are using:
https://docs.gradle.org/current/userguide/dependency_verification.html
Dawid (or anyone), why are we using something different? Is our mechanism
completely defined ad-hoc in
