maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <>
Subject [jira] [Updated] (MNG-6102) Introduce ${maven.conf} in m2.conf
Date Thu, 23 Feb 2017 15:01:01 GMT


Stephen Connolly updated MNG-6102:
    Fix Version/s: 3.5.0-alpha-2

> Introduce ${maven.conf} in m2.conf
> ----------------------------------
>                 Key: MNG-6102
>                 URL:
>             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.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
> 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|]
or [{{heir(7)}}|]. 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

View raw message