Good news: Michael Osipov reports in the comments that this issue should go away with the fixes for concurrency issues that are coming up in Maven 3.9.0.
Nils. > Op 28 feb. 2022, om 01:04 heeft Nils Breunese <n...@breun.nl> het volgende > geschreven: > > After reading the various responses to this thread with people recognizing > this issue on various operating systems, I’ve opened an issue in the Maven > issue tracker: https://issues.apache.org/jira/browse/MNG-7425 > > Nils. > >> Op 18 feb. 2022, om 13:43 heeft Nils Breunese <n...@breun.nl> het volgende >> geschreven: >> >> 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
