Thank you for this information. It is a bit misleading that the line says "as introduced" (past tense) for a release that actually does not exist yet. Would it be OK if I file a PR to clarify that? What is the anticipated release date of Maven 3.7.0 that I could announce there? -Markus
-----Ursprüngliche Nachricht----- Von: John Patrick <nhoj.patr...@gmail.com> Gesendet: Montag, 26. Oktober 2020 12:07 An: Maven Users List <users@maven.apache.org> Betreff: Re: Maven Dependency Plugin If you read the opening line it talks about Maven 3.7.0, which is not yet released. If you want to use a maven wrapper before v3.7.0, then use this https://github.com/takari/maven-wrapper. The upgrade from takari to maven is easy but does allow you to change your documentation, process and ci process instead of waiting until v3.7.0. I did test the maven-wrapper-plugin a few months ago and I had to add a staging repo of something like this before it worked https://repository.apache.org/service/local/repositories/maven-XXX/content/. But can't remember what XXX it was as I've got ~10 in my settings.xml commented out. John On Mon, 26 Oct 2020 at 10:53, Markus Karg <k...@quipsy.de> wrote: > > When I am using this plugin > https://maven.apache.org/plugins/maven-wrapper-plugin/ then Maven fails > because it apparently cannot find needed runtime files on Maven Central. This > limitation is not told on that page. Is that a bug or am I doing something > wrong? > -Markus > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
