[MNG-5659] Project specific settings.xml

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-7, 4.0.0
• Component/s: FDPFC
• Assignee: Guillaume Nodet
• Reporter: Joachim Van der Auwera
• Created: 02/Jul/14 09:40
• Updated: 20/Oct/23 07:57
• Resolved: 19/Jun/23 10:32

Description

It would be useful to have a settings.xml file next to the project pom that could contain project specific settings. For example, when switching between projects it is sometimes necessary to also change the location of the local repository, or use a different set of repositories and/or mirror settings for each project.

If a settings.xml file could be included with a project checkout, then the repositories needed for the build could be included (instead of putting them in the pom) along with any other project specific settings.

The tricky part is intelligently handling multi-module projects. For a multi-module project I don't want to include a separate settings.xml file for each directory. So Maven could recursively check each parent directory until it either (1) finds a settings.xml, (2) finds a directory with no pom.xml, or (3) finds the root directory.

Issue Links

• fixes: MNG-6327 Add ability to easily retrieve core extensions from alternative pluginRepository
• is duplicated by: MNG-6392 Add Project Settings .mvn/settings.xml
• is related to: MNG-6303 Interpolate user supplied properties and command line arguments
• is related to: MNG-6762 Multimodule project with .mvn/settings.xml not working properly
• is related to: MNG-4060 Remove support for profiles.xml
• links to: GitHub Pull Request #265
• links to: GitHub Pull Request #839
• links to: GitHub Pull Request #1059
• mentioned in: Page Loading...