[ https://issues.apache.org/jira/browse/MNG-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710838#comment-17710838 ]
Delany commented on MNG-5659: ----------------------------- I'm not sure I understand/agree with your example (a username is surely a property for the ${user.home}/.m2/settings.xml file?) but I understand the headache. I've made sure the settings.xml file doesn't change all that often. I think since settings can have server credentials it was always intended that they be provisioned separately. And if it does have a valid reason for changing, like cycling credentials, then its worth setting up puppet/ansible/etc to manage the file. The fact that --settings switch can refer to a project file looks like a hack. Since a temporary Jenkins workspace doesn't have a user.home I'm guessing this was added to override that location. In short I don't think this issue should be pursued. For a project-specific local repository add -Dmaven.repo.local to .mvn/maven.config, and for alternative repositories use either a setting profile or a project profile. > Project specific settings.xml > ----------------------------- > > Key: MNG-5659 > URL: https://issues.apache.org/jira/browse/MNG-5659 > Project: Maven > Issue Type: New Feature > Components: FDPFC > Reporter: Joachim Van der Auwera > Priority: Major > Fix For: Issues to be reviewed for 4.x > > Attachments: mvn.patch > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)