[
https://issues.apache.org/jira/browse/MWRAPPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850078#comment-17850078
]
Nils Breunese commented on MWRAPPER-110:
----------------------------------------
We use Maven Wrapper type {{bin}}, because our JDK build image doesn't contain
{{curl}} or {{wget}}, so moving to {{only-script}} is not immediately an option
for us. We migrated from {{MAVEN_CONFIG}} to {{MAVEN_ARGS}} because
{{MAVEN_CONFIG}} is no longer read since Maven Wrapper 3.3.0 (MWRAPPER-133),
but now it turns out that {{MAVEN_ARGS}} also doesn't work when calling Maven
via {{./mvnw}}. We really need an environment variable to pass Maven CLI
arguments, so support for {{MAVEN_ARGS}} would be really appreciated, or are
there any other options for us?
> 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)
