You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/02/21 19:06:00 UTC
[jira] [Closed] (MNG-6606) Allow installation-wide parameter customization
[ https://issues.apache.org/jira/browse/MNG-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MNG-6606.
-------------------------------
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
Resolution: Incomplete
No valid feedback for almost three years.
> Allow installation-wide parameter customization
> -----------------------------------------------
>
> Key: MNG-6606
> URL: https://issues.apache.org/jira/browse/MNG-6606
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.1.1
> Reporter: Paul Benedict
> Priority: Major
>
> In my use case, I would like to always print the version of Maven at every execution. I am not interested in a per-project case basis; nor interested in modifying the startup batch scripts. I want to drop in a standard configuration file to control all my Maven installations in the same manner.
> My request is to make {{/.mvn/maven.config}} and {{./mvn/}}{{mavenrc}} to also be recognized in the Maven installation root. I am not explicitly asking for {{${maven.root}/.mvn}} to beĀ *the* solution, but it's the right place to start the problem solving.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)