Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.2.x (to be reviewed)
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Artifacts and Repositories
-
Labels:None
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
-
-
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
-
-
MNG-4353
[regression] Plugin dependencies are not downloaded from repos given in the plugin's POM
-
-
MNG-4413
[regression] Repositories discovered in dependency POMs are not subject to mirroring
-
-
MNG-4710
Command line option to use dependency repositories
-
This can't change for 2.0.x but it does make resolution unpredictable. Repositories need to be all gathered prior to resolution. The repositories should be removed from the model in 2.1.