[ https://issues.apache.org/jira/browse/MNG-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811262#comment-17811262 ]
Herve Boutemy commented on MNG-7980: ------------------------------------ FTR, such a use case of making sure remote repositories are perfectly managed is until now done by defining mirrorOf * or external:* in settings: https://maven.apache.org/guides/mini/guide-mirror-settings.html > Add ability to ignore transitive dependency repositories: mvn -itr > ------------------------------------------------------------------ > > Key: MNG-7980 > URL: https://issues.apache.org/jira/browse/MNG-7980 > Project: Maven > Issue Type: Improvement > Components: Core > Reporter: Tamas Cservenak > Assignee: Tamas Cservenak > Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-12 > > > In certain cases it is valid to ignore repositories introduced by transitive > dependencies. They are usually needed, but in certain cases (ie. air gapped > environment) they are just causing problems. Even if environment, or the POM > itself defines all the repositories needed for the build (so the "superset" > of remote repositories that have all the artifacts the build even needs), > this requires tuning in case of dependency changes, as new and new > repositories may be introduced as dependencies change. > Ideally, Maven could be instructed to globally ignore any repository > introduced by dependency, as POM itself has it call (in controlled fashion) > to fulfil all the artifacts. > => add CLI option to {{mvn}} command: {{-itr}}, > {{ignore-transitive-repositories}} > https://maven.apache.org/ref/4.0.0-alpha-12/maven-embedder/cli.html -- This message was sent by Atlassian Jira (v8.20.10#820010)