[ 
https://issues.apache.org/jira/browse/MNG-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864926#comment-17864926
 ] 

ASF GitHub Bot commented on MNG-7914:
-------------------------------------

gnodet commented on PR #1595:
URL: https://github.com/apache/maven/pull/1595#issuecomment-2222153855

   > my test in project `.mvn/maven.properties` with content:
   > 
   > ```
   > ${includes}=default.properties,?env-${env:envName}.properties
   > ```
   > 
   > looks like `${env...}` is not interpolated in project properties
   > 
   > executed:
   > 
   > ```
   > envName=test mvn ...
   > ```
   > 
   > It will be great to support user properties in such case to have a 
possibility:
   > 
   > ```
   > ${includes}=default.properties,?env-${envName}.properties
   > ```
   > 
   > and
   > 
   > ```
   > mvn -DenvName=test ...
   > ```
   
   I've added a unit test showing this now works.




> Provide a single entry point for configuration
> ----------------------------------------------
>
>                 Key: MNG-7914
>                 URL: https://issues.apache.org/jira/browse/MNG-7914
>             Project: Maven
>          Issue Type: New Feature
>            Reporter: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.x-candidate
>
>
> Looking at MNG-7772, this should not require any code change, but it's all 
> about configuration.
> I propose to load / interpolate the following files:
>  * {{${maven.home}/conf/maven.user.properties}}
>  * {{${maven.home}/conf/maven.system.properties}}
> Those files would be used to load additional user properties and system 
> properties for Maven.  In addition to the simple interpolation mechanism, we 
> should provide two enhancements using special keys {{{}$\{includes{}}}} and 
> {{{}$\{optionals{}}}} which would be used to load additional referenced 
> configuration files such as:
> {{    ${optionals} = ${user.home}/.m2/maven.user.properties, 
> ${session.rootDirectory}/.mvn/maven.user.properties}}
> Being loaded early when Maven is loaded, those files could reference 
> directories to load extensions from:
>   {{{}maven.core.extensions.directories = 
> ${session.rootDirectory}/.mvn/extensions.xml,{}}}{{{}${user.home}/.m2/extensions.xml,${maven.home}/extensions.xml{}}}
>  
> In various places, the maven code could be simplified and offer more 
> configuration points at the same time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to