This will be part of 3.7.0 together with other huge changes. Having the wrapper makes it possible to start updating the defaults for our Maven plugins. I don't expect a release soon and I don't see a reason to hurry that. We've done 3.6.2 and a 3.6.3 regression release to give us time to work on 3.7.0.
Robert On 18-2-2020 18:50:01, Manfred Moser <manf...@simpligility.com> wrote: Agreed... if you think now is a good time, I am happy to update the Takari repos with a redirect to the maven dev list and the sandbox repo for now. I plan to close all issues and all PR and declare the project inactive and moved to Apache Maven upstream. Just not sure what the best timing for that is. And in terms of getting the scripts in a separate repo or Maven core ... I see good reasons for both and dont really have a preference. I just would love to get it moved and into main Maven as soon as possible. Would we cut 3.6.4 when the wrapper is done in core? Manfred Robert Scholte wrote on 2020-02-16 04:13 (GMT -08:00): > I want to prevent legal issues, so I won't pick up PRs from that repository. > Once the Maven Wrapper has it's final location, one can provide new PRs on our > codebase. > > Robert > On 16-2-2020 12:56:55, James Gao wrote: > On Sun, Feb 16, 2020 at 5:50 PM Robert Scholte wrote: > >> I've found another reason to move it to core: the mvnw scripts are >> extended versions of the mvn scripts. >> If you do a diff, you'll recognize a block responsible for downloading the >> wrapper jar. >> But you also notice that all recent improvements on the mvn scripts have >> not been adopted. >> If you use the mvnw for Maven x.y.z, it should behalve as calling mvn of >> Maven x.y.z, now it doesn't. >> > > Hi Robert, there is a PR to > integrate the new boot behavior from maven core to the original wrapper. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
