[MNG-6102] Introduce ${maven.conf} in m2.conf

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.9
• Fix Version/s: 3.5.0-alpha-1, 3.5.0
• Component/s: Bootstrap & Build, core, Settings, Toolchains
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 08/Oct/16 09:55
• Updated: 23/Feb/17 15:02
• Resolved: 24/Jan/17 17:33

Description

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.

Issue Links

• mentioned in: Page Loading...