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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Component/s: Artifacts and Repositories
• Assignee: Jason van Zyl
• Reporter: Wendy Smoak
• Created: 14/Jun/07 21:30
• Updated: 08/Feb/20 15:41
• Resolved: 19/Jan/14 13:09

Description

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.

Issue Links

• is related to: MNG-3384 Repos defined in plugin are used to download dependencies
• is related to: MNG-4420 It should be possible to define your mirrors section inside a profile
• relates to: MNG-3052 Transitive Dependency not found when repo is not listed
• relates to: MNG-4353 [regression] Plugin dependencies are not downloaded from repos given in the plugin's POM
• relates to: MNG-4413 [regression] Repositories discovered in dependency POMs are not subject to mirroring
• relates to: MNG-4710 Command line option to use dependency repositories