You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2021/12/26 17:16:00 UTC

[jira] [Commented] (MWRAPPER-14) Make maven wrapper functional

    [ https://issues.apache.org/jira/browse/MWRAPPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465404#comment-17465404 ] 

Herve Boutemy commented on MWRAPPER-14:
---------------------------------------

wrapper removed from Maven Core in https://github.com/apache/maven/commit/f793d862e3158f8dde98f00905f907b6bd5e0aaf and ITs in https://github.com/apache/maven-integration-testing/commit/1ce55e0cb8b41d3930512a8aac25b51548a16701

> Make maven wrapper functional
> -----------------------------
>
>                 Key: MWRAPPER-14
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-14
>             Project: Maven Wrapper
>          Issue Type: Task
>    Affects Versions: 3.0.2
>            Reporter: Tamás Cservenák
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 3.1.0
>
>
> Make a wrapper a normal wrapper. The wrapper is not meant to be part of any distribution, but a lightweight way to bootstrap maven without the need to install it onto target machine.
> With legacy wrapper:
>  * checked out project "just works"
>  * you know it builds with proper maven
>  * exclude any mistake like install ancient mvn version or some distro mutilated mvn
> This is the main goal, and by having apache groupId, {{wrapper:wrapper}} should work like before.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)