Maven resolver seems to be slower than the Coursier resolver about rules_jvm_external HOT 2 CLOSED

You can get additional logging by running the resolution with the adding RJE_VERBOSE=1 to the environment variables. If the information this provides doesn't help much, I can add some additional logging to the next rules_jvm_external release.

There are also some other environment variables you might want to play with.

from rules_jvm_external.

@shs96c I got some time to dig into this today and it turned out to be an issue in our configuration.

We didn't have execution mode set, so it was running REPIN=1 bazel run @maven://pin on every item on the change request.

So, if we had one PR for AWS deps with like 30 deps, it would try to run it 30 times...

I am not sure how Coursier survived this, but I guess it had some sort of caching in place.

I guess this is a new config option that was added and we were using an older image and we ended up with a new image when I made changes to the syncing script.

Thanks to your suggestion, I also started using RJE_MAX_THREADS and RJE_UNSAFE_CACHE. RJE_ASSUME_PRESENT didn't really work and I didn't get time to look into it in depth.

Apologies for the trouble and thanks for the tips!!

from rules_jvm_external.