[
https://jira.codehaus.org/browse/MNG-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349096#comment-349096
]
Joachim Van der Auwera commented on MNG-5659:
---------------------------------------------
This is a clone of MNG-4686.
I have been using this solution for a long time now and find it very useful.
I think it would be very useful to have local maven settings. For contractors
(like myself) there are settings for specific clients and settings I need for
other projects. It would be very useful to have some kind of project specific
overrid of maven settings. In many cases, these could even be put under source
control.
If there is something missing in this issue to accept the patch, I would gladly
try to improve it to meet project standards.
> Project specific settings.xml
> -----------------------------
>
> Key: MNG-5659
> URL: https://jira.codehaus.org/browse/MNG-5659
> Project: Maven
> Issue Type: New Feature
> Reporter: Joachim Van der Auwera
> 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
(v6.1.6#6162)
