[
https://jira.codehaus.org/browse/MNG-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340281#comment-340281
]
Joseph Walton commented on MNG-3056:
------------------------------------
For anyone looking for how to force resolution through a single URL, it's under
[Using A Single
Repository|http://maven.apache.org/guides/mini/guide-mirror-settings.html]. Add
a mirror to your {{~/.m2/settings.xml}} with {{mirrorOf}} set to {{*}}:
{noformat}
<settings>
...
<mirrors>
<mirror>
<id>internal-repository</id>
<name>Maven Repository Manager running on repo.mycompany.com</name>
<url>http://repo.mycompany.com/proxy</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
...
</settings>
{noformat}
> Dependencies should not be able to introduce repositories to the build
> ----------------------------------------------------------------------
>
> Key: MNG-3056
> URL: https://jira.codehaus.org/browse/MNG-3056
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.x (to be reviewed)
> Reporter: Wendy Smoak
> Assignee: Jason van Zyl
> Fix For: Issues to be reviewed for 3.x
>
>
> If you depend on an artifact that has repositories or pluginRepositories
> defined in the pom, those repositories are also searched for artifacts.
> It's disconcerting when you think you've overridden 'central' and set things
> up to use only internal repositories, and Maven still tries to to download
> artifacts from elsewhere.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
