Am 2023-04-22 um 21:36 schrieb Jeremy Landis:
Thank you, Tamas! That did the trick. Thank you for detailed explanation of
what is going on.
I simply added to maven.config
-Daether.connector.smartChecksums=false
And now it is doing exactly what I got when maven 3.8.x and before. I do have
the checksums algorithms set as indicated and personally would love to remove
the older ones but as noted everything would need there and in our platforms we
still have some md5 even so I need all unfortunately. One day I'm sure that
will change. Thanks for noting you will extend documentation, that will
significantly help others I'm sure. At the moment, we are not actually doing
anything with the checksums and I discovered it while researching separate
issue few weeks back as we have a lot of network problems in general due to
large scale / limited resources. Ultimately, we plan to start verifications
and it was somewhat perplexing. For us, we are planning on jacking up the
default retries from 3 to 10 on failed pulls due to varied network issues (as
to my original issue) and seeing checksum issue concerned me if that would even
work given same module and recent add of that logic to the resolver. Now I
feel more confident.
Looking forward to maven 3.9.2 otherwise when it lands. For my day job, we
already have this scaled out on 2k repos at 3.9.1 and I've been doing same with
maven wrapper across all OSS projects I work and will continue doing so.
Loving the overall progress of maven!
Please read about the illusions of checksums:
https://maven.apache.org/resolver/about-checksums.html
