[
https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240516#comment-16240516
]
Konrad Windszus commented on MNG-6303:
--------------------------------------
A potential fix could be to replace
https://github.com/apache/maven/blob/master/apache-maven/src/bin/mvn#L170 by
{code}
cat "$1" | echo | tr -s '\n' ' '
{code}
That would allow basically every bourne shell feature to be used within at
least the {{.mvn/jvm.config}}.
> .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
>
> 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
(v6.4.14#64029)
