Is there any reason not to use the lock_file and fail_if_repin_required in the maven.install of the MODULE.bazel?
I understand that you have to run an additional re-pin command if the dependency was updated.
But this allows us to use the native Bazel downloader instead of Courcier.
Our use case is to use grpc-java as a Bazel 9 module. And with the Courcier, we have to download Maven artifacts from the https://repo.maven.apache.org/maven2/ each time. This fact makes our CI builds unstable. And we can't benefit from --repository_cache (local cache on each CI worker) or --downloader_config (rewriting repo.maven.apache.org to the private proxy).
Is there any reason not to use the
lock_fileandfail_if_repin_requiredin themaven.installof theMODULE.bazel?I understand that you have to run an additional re-pin command if the dependency was updated.
But this allows us to use the native Bazel downloader instead of Courcier.
Our use case is to use grpc-java as a Bazel 9 module. And with the Courcier, we have to download Maven artifacts from the
https://repo.maven.apache.org/maven2/each time. This fact makes our CI builds unstable. And we can't benefit from--repository_cache(local cache on each CI worker) or--downloader_config(rewritingrepo.maven.apache.orgto the private proxy).