[ https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871082#comment-16871082 ]
Konrad Windszus commented on MNG-6303: -------------------------------------- [~breun] Thanks for the hint. Since this requirement is broader (i.e. not limited to a custom settings.xml filename) I think this is the more relevant issue. Once this is solved, this can be used to achieve the requirement from MNG-5659 as well. > .mvn/jvm.config should allow to resolve environment variables > ------------------------------------------------------------- > > Key: MNG-6303 > URL: https://issues.apache.org/jira/browse/MNG-6303 > Project: Maven > Issue Type: Bug > Components: Bootstrap & Build > Affects Versions: 3.5.0 > Reporter: Konrad Windszus > Priority: Major > > 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 (v7.6.3#76005)