The "verifyLocks" is in gradle... but in Lucene/ Solr it's actually done by the palantir's plugin: https://github.com/palantir/gradle-consistent-versions
To quote from their site: "There is a verifyLocks task (automatically run as part of check) that will ensure versions.lock is still consistent with the current dependencies." If you change the global dependency in versions.props the versions.lock file needs to be updated manually via --write-locks, as explained here: https://github.com/apache/lucene/blob/main/help/dependencies.txt#L50-L59 Can I ask why you need to rewrite gradle to gradle so that the other build system works? This seems a tad insane? Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
