[
https://issues.apache.org/jira/browse/MNG-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004042#comment-15004042
]
Jason van Zyl commented on MNG-5930:
------------------------------------
This is by design. The maven.config is for Maven flags, not system properties.
Right now all of this is handled in startup scripts so there is unlikely to be
any facility for interpolation.
> .mvn/maven.config does not expand environmental variables
> ---------------------------------------------------------
>
> Key: MNG-5930
> URL: https://issues.apache.org/jira/browse/MNG-5930
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.3
> Environment: Linux mint 17.2
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> Reporter: William Buss
>
> environmental variables used in .mvn/maven.config are not expanded out.
> running
> mvn clean install -Dmaven.repo.local=$HOME/.m2/otherRepo
> correctly creates and uses the local repo in /home/user/.m2/otherRepo
> if the argument -Dmaven.repo.local=$HOME/.m2/otherRepo, is placed in the
> .mvn/maven.config file, then the local repo used is
> current working directory/$HOME/.m2/otherRepo
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
