[jira] (MNG-3056) Dependencies should not be able to introduce repositories to the build

["Joseph Walton (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305676#comment-305676 ] 

Joseph Walton commented on MNG-3056:
------------------------------------

We're using a dependency with a repository definition that points to a URL that no longer resolves. The workaround is to redefine that repository ID with a real repository in our {{settings.xml}}, but it would be great to be able to pass a flag on the command line to ensure that only the repositories defined in our settings are used.

                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira