Downloading by the plugin works different compared to the takari-maven-plugin.
The takari-maven-plugin was downloading a URL, whereas the maven-wrapper-plugin
is downloading an artifact using the artifact resolver libraries, so these are
settings.xml-aware.
Would be nice to confirm this.
Robert
Hi Robert,
this is slightly offtopic but since you wrote:
On the other hand, the plugin must be able to download the apache-maven-wrapper
distribution.
Is this integration into Maven also adressing proxy handling for the
download?
I am asking because I had to add special handling to Quarkus t
To be clear: it is just a bootstrapping issue.
Once all is in place they can both have their own release cycle.
The plugin won't need to be released before every Maven Core release, as it can
pick up the Maven version from the runtime.
It is actually possible to run the plugin with 3.0 if we want
Now that maven-wrapper is available in master of maven-core, the next step
would be to make it easy to use.
I've created MNG-6917[1] to make it possible to simply call {{mvn wrapper}}
However, this requires the plugin to be available.
On the other hand, the plugin must be able to download the apac
