Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.5.0
-
None
Description
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
Attachments
Issue Links
- duplicates
-
MNG-5930 .mvn/maven.config does not expand environmental variables
- Closed
- is duplicated by
-
MNG-5859 Apply filter to .mvn/maven.config
- Closed
-
MNG-5930 .mvn/maven.config does not expand environmental variables
- Closed
- relates to
-
MNG-5659 Project specific settings.xml
- Closed
-
MNG-5767 project-specific default jvm options and command line parameters
- Closed
-
MNG-6267 Support resolving "~" in values given to CLI Option "-s"
- Closed
-
MRESOLVER-304 DirectoryUtils should consider interpolation
- Closed
-
MNG-7774 Maven config and command line interpolation
- Closed
- links to