[ https://issues.apache.org/jira/browse/MNG-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710322#comment-17710322 ]
Delany commented on MNG-5659: ----------------------------- What situation would necessitate project-specific mirrors? If the requirement is to facilitate more granular settings and not just to ease the distribution of Maven settings, then what about considering a new concept: project group. Settings could be defined to apply for any project within a directory {code:java} <settings> <projectGroups> <projectGroup> <directory>/git/github</directory> <mirror> <id>extra</id> <url>https://nexus.puff.com/repository/extra/</url> <mirrorOf>central</mirrorOf> </mirror> <projectGroup> <projectGroups> <localRepository/> <interactiveMode/> <offline/> <pluginGroups/> <servers/> <mirrors/> <proxies/> <profiles/> <activeProfiles/> </settings> {code} Or just make every settings.xml file apply to a path and introduce recursion {code:java} <settings> <path>/git</path> <localRepository/> <interactiveMode/> <offline/> <pluginGroups/> <servers/> <mirrors/> <proxies/> <profiles/> <activeProfiles/> <settings> <path>/git/github</path> <mirror> <id>extra</id> <url>https://nexus.puff.com/repository/extra/</url> <mirrorOf>central</mirrorOf> </mirror> </settings> </settings> {code} > 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)