[jira] [Commented] (MNG-7193) Introduce MAVEN_ARGS environment variable

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-7193:
-------------------------------------

Fixed with [29c53d67483445094270740477fa8909b6fd9f85|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=29c53d67483445094270740477fa8909b6fd9f85] for {{maven-3.9.x}} branch.

> Introduce MAVEN_ARGS environment variable
> -----------------------------------------
>
>                 Key: MNG-7193
>                 URL: https://issues.apache.org/jira/browse/MNG-7193
>             Project: Maven
>          Issue Type: New Feature
>          Components: Command Line
>    Affects Versions: 3.8.1
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 4.0.0-alpha-1, 4.0.0
>
>
> Over the last couple of years people demanded to always pass arguments down to Maven without supplying it specifically or repeat for every project over and over again in {{maven.config}}. Arguments like {{-B}} or {{-V}}.
> A new environment variable {{MAVEN_ARGS}} can be passed *before* the actual CLI arguments.
> Ideal precedence:
> {{MAVEN_ARGS}} is overwritten by {{maven.config}} is overwritten by CLI arguments. General to specific. Unfortunately, since {{MAVEN_ARGS}} will be passed just like CLI arguments there is no way to detect that these arguments came either via CLI or {{MAVEN_ARGS}}
> One option would be to add separator token which would be dropped internally thus makes it possible to differentiate between both, e.g,, {{MAVEN_ARGS_START [ARGS...] MAVEN_ARGS_STOP}}. 



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