You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/08/11 19:03:20 UTC
[jira] [Updated] (MNG-5930) .mvn/maven.config does not expand
environmental variables
[ https://issues.apache.org/jira/browse/MNG-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise updated MNG-5930:
-------------------------------------
Priority: Minor (was: Major)
> .mvn/maven.config does not expand environmental variables
> ---------------------------------------------------------
>
> Key: MNG-5930
> URL: https://issues.apache.org/jira/browse/MNG-5930
> Project: Maven
> Issue Type: New Feature
> 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
> Priority: Minor
>
> 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)