[
https://issues.apache.org/jira/browse/MNG-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710902#comment-17710902
]
Delany commented on MNG-5659:
-----------------------------
There's a section on using profiles to configure repositories:
[https://maven.apache.org/guides/mini/guide-multiple-repositories.html]
In your global settings you could place the default repository in a profile
that only activates when a property is not set, and then set that property in
your .mvn/maven.config for the project's you're working on. (Note: never use
activateProfiles, as it turns all other profiles off. This should probably be
deprecated). Now your project has control over the global settings repository
via a property. Feel free to add your own repository directly or via a profile.
I don't think we ever activate a profile using -P anymore. There's always some
other property/file/package type that turns it on. One benefit is that profiles
linked to a property can be mutually exclusive.
> 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)
