You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 15:00:03 UTC

[jira] [Commented] (MNG-6102) Introduce ${maven.conf} in m2.conf

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

Hudson commented on MNG-6102:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> 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 &amp; Build, core, Settings, Toolchains
>    Affects Versions: 3.3.9
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.5.0-alpha-1, 3.5.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
(v8.3.4#803005)