[
https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863792#comment-16863792
]
Konrad Windszus commented on MNG-6303:
--------------------------------------
Actually my main use case is to use a project-specific settings.xml which
should be shared via a source code repository (e.g. Git). It would make sense
to distribute that also within the {{.mvn}} directory but it is impossible to
reference such a file correctly, because the absolute path name differs per
user and relative path names always refer to the {{basename}} but not to the
{{.mvn}} directory itself. So together with adding support for environment
variables it would probably make sense to define an environment variable giving
the location of the resolved {{.mvn}} directory.
> .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)
