[
https://issues.apache.org/jira/browse/MNG-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly reopened MNG-6102:
-----------------------------------
Maven 3.4.0 has been dropped. See [this
thread|https://mail-archives.apache.org/mod_mbox/maven-dev/201701.mbox/%3CCA%2BnPnMx-e7kGYy3Hp87v8hLGdhp1q%3DtKLx_6QuZ4kGUqHEBGcw%40mail.gmail.com%3E]
for more details.
This issue will need to be re-scheduled for a Maven release in the (hopefully
near) future.
> 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}}
> property 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}} property 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)
