Jacques Etienne Beaudet <jebeau...@gmail.com> wrote: > Maven repository is not safe when running multiple concurrent builds (not the > -T1C option). You need to use an external synchronization technique if you > need this. > https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html
I’ve asked my colleagues, but they weren’t doing parallel builds (-T or --threads). Nils. > Not sure of the implications of assuming an empty zip file means a failed > download, it seems reasonable to me but I'll let others chip in. > On Feb 18, 2022, 7:43 AM -0500, Nils Breunese <n...@breun.nl>, wrote: >> Hi, >> >> I’ve been encountering Maven warnings like these for years from time to time: >> >> ---- >> WARN: zip file is empty: >> /Users/username/.m2/repository/com/example/example-artifact/1.2.3/example-artifact-1.2.3.jar >> java.util.zip.ZipException: zip file is empty >> ---- >> >> I know that when I encounter this I can just delete the file and run Maven >> again and then it’ll generally download ok, but recently I’ve been getting >> questions from a lot of colleagues with this issue. I was wondering: would >> it make sense for Maven to assume that an empty JAR file was not downloaded >> correctly and try re-downloading it automatically? >> >> Nils. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
