[jira] [Comment Edited] (MNG-5659) Project specific settings.xml

["James Z.M. Gao (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678077#comment-17678077 ] 

James Z.M. Gao edited comment on MNG-5659 at 1/18/23 5:52 AM:
--------------------------------------------------------------

Hi [~triathlon98] , did you try the extension solution in the issue MNG-6392?


was (Author: gzm55):
Hi [~triathlon98] , did you try the extension solution in the issue [#MNG-6392]?

> 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)