[
https://issues.apache.org/jira/browse/MWRAPPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850125#comment-17850125
]
Nils Breunese edited comment on MWRAPPER-110 at 5/28/24 6:10 PM:
-----------------------------------------------------------------
I just found that {{MAVEN_CONFIG}} still gets read when using Maven Wrapper
3.3.0+ with the {{bin}} type, but {{MAVEN_CONFIG}} doesn't get read when using
the new default {{only-script}} type.
And when you use {{only-script}}, you can use {{MAVEN_ARGS}}. But that doesn't
work with the {{bin}} type.
Is it intentional that what environment variable you can use depends on the
Maven Wrapper distribution type? Because I think the current situation is
pretty confusing.
was (Author: breun):
I just found that {{MAVEN_CONFIG}} still gets read when using Maven Wrapper
3.3.0+ with the {{bin}} type, but {{MAVEN_CONFIG}} doesn't get read when using
the new default {{only-script}} type.
And when you use {{only-script}}, you should use {{MAVEN_ARGS}}? Which doesn't
work with the {{bin}} type? This is all pretty confusing.
> 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)
