On Tue, Dec 10, 2024 at 8:23 AM Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote: > > Hi Gary, > > On 10.12.2024 13:23, Gary Gregory wrote: > > sh mvnw verify \ > > -Prelease artifact:compare \ > > > > -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 > > Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper > > might be compromised. > > Investigate or delete > > /Users/garydgregory/rc/log4j-2.24.3/src/.mvn/wrapper/maven-wrapper.jar > > to attempt a clean download. > > If you updated your Maven version, you need to update the specified > > wrapperSha256Sum property. > > Could you investigate what is going on, e.g. with: > > MVNW_VERBOSE=true sh mvnw validate -N
Running: set MVNW_VERBOSE=true && sh mvnw validate -N Says: Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be compromised. Investigate or delete /Users/garydgregory/rc/log4j-2.24.3/src/.mvn/wrapper/maven-wrapper.jar to attempt a clean download. If you updated your Maven version, you need to update the specified wrapperSha256Sum property. So let's forget about mvnw, it's not reliable and why would I want to get a ton of old jars in my Maven cache... Running 'mvn validate -N' and 'mvn validate' succeeds. Running 'mvn clean verify' succeeds, so +1. Gary > > > zsh: no such file or directory: > > -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1309 > > That seems strange, why did`zsh` interpret the last argument as separate > command? Maybe you have a space after line continuation character \ ? Maybe there was a problem copy-pasting from the review guide. I made it all on one line. > > Piotr >
