You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/04/26 13:56:00 UTC

[jira] [Updated] (MNG-6303) .mvn/jvm.config and .mvn/maven.config should allow to resolve environment variables

     [ https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MNG-6303:
---------------------------------
    Fix Version/s: 3.9.2
                   4.0.0-alpha-6
                   4.0.0

> .mvn/jvm.config and .mvn/maven.config should allow to resolve environment variables
> -----------------------------------------------------------------------------------
>
>                 Key: MNG-6303
>                 URL: https://issues.apache.org/jira/browse/MNG-6303
>             Project: Maven
>          Issue Type: New Feature
>          Components: Bootstrap &amp; Build
>    Affects Versions: 3.5.0
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: 3.9.2, 4.0.0-alpha-6, 4.0.0
>
>
> With the mechanism of having project-specific maven options being specified in {{.mvn/maven.config}} and {{.mvn/jvm.config}} (MNG-6267) it is often handy to share those settings among multiple developers (i.e. via maintaining it via the SCM). Unfortunately the mechanism does not support resolving environment variables, which makes it hard to deal with user-specific directories or settings. Please support resolving environment variables through a special pattern like {{$ENV_NAME}}



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