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

Roy Teeuwen commented on MNG-5659:
----------------------------------

I'm facing the same issue as a contractor. A logical way I would see this work 
is to be able to specify a settings file per folder:

~/workspace/client-one/settings.xml
~/workspace/client-two/settings.xml

I have looked into making a core extension for this, but the issue is that you 
can't easily load in core extensions on a global level. You could add them to 
the ${maven.home}/lib/ext, but on an update of maven this extension would then 
disappear. It would be easier if you could load them also in through for 
example ${user.home}/.m2/lib/ext

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

Reply via email to