Guillaume Nodet

> > `UnusedLocalVariable` are plain wrong imho > > convention tells them to be named accordingly like unused or ignored just like error-prone does. > > * https://maven.apache.org/ref/3.9.11/maven-core/xref/org/apache/maven/lifecycle/internal/MojoExecutor.html#L313 > >...

> > and calling it `unused` would be wrong imho. > > Yes, also allowed to be called `ignored` then. > > In this case — actually, also in general,...

IMHO, Maven Wrapper should support `mvnd`, so I think it's more an issue for Maven Wrapper rather than mvnd.

I think the current raised PRs solve most problems. The remaining one is the resolver dependency tracker (`bf` consumes more resources than `df` but provides _correct_ results).

> [@gnodet](https://github.com/gnodet) feel free to close whenever you see fit. I didn't have time to follow up on this unfortunately. Yeah, I'll keep it opened until the PRs are merged:...

Sure, could you write a script that does that ?

> The files I see here are already signed https://downloads.apache.org/maven/mvnd/1.0.2/ > > How do they get there? Where are they signed? > > Using the script build/release-candidate.sh which should be...

> Maven Central requires artefacts to be signed. Question if it's allowed by ASF policy, to store pgp keys used to sign outside of your own release manager workstation? I...

> > The files I see here are already signed https://downloads.apache.org/maven/mvnd/1.0.2/ > > How do they get there? Where are they signed? > > Using the script build/release-candidate.sh which should...

> > The release process is documented at https://github.com/apache/maven-mvnd/blob/master/RELEASING.adoc > > I'm open to any change, as long as it can be scripted. > > Looking at the scripting I...