[
https://issues.apache.org/jira/browse/MWRAPPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850131#comment-17850131
]
Tamas Cservenak commented on MWRAPPER-110:
------------------------------------------
Certainly not. The wrapper was "inherited" from Takari project, and
MAVEN_CONFIG was their feat (undocumented and not documented as proper Maven
config either). The "script" basically delegates to Maven proper, so it
supports things listed here [https://maven.apache.org/configure.html]
Basically, we need to fix and align these (as much as possible) on "proper"
(documented) configuration ways.
> 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)
