Michael Osipov created MNG-6102:
-----------------------------------
Summary: Introduce maven.conf in m2.conf
Key: MNG-6102
URL: https://issues.apache.org/jira/browse/MNG-6102
Project: Maven
Issue Type: Improvement
Components: Bootstrap & Build, core, Settings, Toolchains
Affects Versions: 3.3.9
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.4.0
Package maintainers always try to fit a product into the file hierarchy
given/mandated by the OS/distribution. They separate the application from the
configuration to have one common place for every bit. Currently, Maven does not
properly support his. {{conf/}} is tightly coupled with {{maven.home}} and
cannot be changed unless the Java code changes. Impossible for a maintainer to
stick to [FHS|https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard] or
[{{heir(7)}}|https://www.freebsd.org/cgi/man.cgi?query=hier&sourceid=opensearch].
By introducing a {{maven.conf}} variable in {{m2.conf}}, a maintainer can
easily move the configuration files to {{/usr/local/etc/maven3}}, decouple it
from the installation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
