[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=17850185#comment-17850185
]
Nils Breunese commented on MWRAPPER-110:
Ok, so the intention is for {{MAVEN_ARGS}} (documented in the Maven
configuration docs) to work with all Maven Wrapper distribution types then? If
so, why was the pull request in this ticket closed?
> 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)
[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=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)
[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=17850125#comment-17850125
]
Nils Breunese commented on MWRAPPER-110:
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.
This is all very 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)
[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=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)
[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=17827744#comment-17827744 ] Tamas Cservenak commented on MWRAPPER-110: -- I recommend making "script-only" the default, as I am using ONLY it and makes sense... > 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)
[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=17827743#comment-17827743 ] Damiano Albani commented on MWRAPPER-110: - Thanks [~sjaranowski], this is indeed a solution. > 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)
[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=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)
