You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/05/01 11:54:00 UTC

[jira] [Commented] (MWRAPPER-110) The Maven 3.9 `MAVEN_ARGS` env var is not supported

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

Slawomir Jaranowski commented on MWRAPPER-110:
----------------------------------------------

Please try new script type:

{noformat}
mvn wrapper:wrapper -Dtype=only-script
{noformat}

It is difficult to implement such feature ... we will need a script for every Maven releases, so easier is use script from Maven distribution.

> The Maven 3.9 `MAVEN_ARGS` env var is not supported
> ---------------------------------------------------
>
>                 Key: MWRAPPER-110
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-110
>             Project: Maven Wrapper
>          Issue Type: Bug
>          Components: Maven Wrapper Scripts
>    Affects Versions: 3.2.0
>            Reporter: Dimitar Dimitrov
>            Priority: Major
>
> If we specify arguments in `MAVEN_ARGS`, they are picked up automatically by `mvn`, but not by `mvnw`.
> Please port this patch: [https://github.com/apache/maven/pull/49]
> A workaround is to export an extra env variable `MAVEN_CONFIG` which is picked by `mvnw`



--
This message was sent by Atlassian Jira
(v8.20.10#820010)