Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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