Update Maven wrapper

[asomov]

No description provided.

[cowtowncoder]

Hi @asomov! Could you elaborate a bit on this one? Is this just a newer recommended version of wrapper or... ? Is there a blog post or article explaining what is the benefit?

[asomov]

@cowtowncoder Maven Wrapper is now not from io/takari but from Apache
The JAR was removed from GIT (I do not like binaries in GIT)
Functionality is identical.

[cowtowncoder]

Ok, but is this basically following a more up-to-date explanation of sort of "standard" Maven wrapper usage?
I would just like to know the source if so, and perhaps make similar changes for other repos.
It is not that I do not trust you or set up but want to know the source.

[asomov]

@cowtowncoder yes, it is just standard way now

[cowtowncoder]

@asomov Before merging this, I really need to see the instructions of how to set this up. All instructions I googled for go with Takari plug-in, f.ex:

• https://dev.to/goffity/install-maven-wrapper-53o8
• http://www.mastertheboss.com/jboss-frameworks/jboss-maven/how-to-use-the-maven-wrapper-in-your-projects/
• https://reflectoring.io/maven-wrapper/

all claim one should use:

mvn -N io.takari:maven:0.7.7:wrapper

and if there is a newer, better way, I want to know that so I can repeat the process.
I cannot (or rather, should not) just copy files if and when there is a process to use to get pieces added.

So... do you know of an article, blog post, github repo that shows how to do this?

[asomov]

@cowtowncoder it was before it became part of Apache (it was takari).
Now it is simpler:

mvn wrapper:wrapper
(make sure you do not add JAR to GIT - it will be downloaded when you run it the first time)

[asomov]

It allows all the developers and the CI use exactly the same version of Maven (the same plugins)

[cowtowncoder]

@asomov Ah! thank you very much. This makes sense. I'll merge this then.

[cowtowncoder]

Ugh. Sorry, I botched this one, trying to rebase and ending up temporarily merging ... yeah. 3.0 stuff in, it seems. Not sure why, actually, but I guess I'll stick to cherry-picking going forward.

Will use generation mechanism suggested on branch 2.13, idea being I'd like to backport this so it's not only used for master (which is for Jackson 3.0.0).