Why are exclusions made on a dependency-by-dependency basis instead of

1.	Why are exclusions made on a dependency-by-dependency basis instead of at the POM level?
Answer» This is primarily to ensure that the dependency GRAPH is predictable, as well as to prevent inheritance effects from ELIMINATING a dependent that should not be EXCLUDED. If you have to use the method of last resort and add an exclusion, make sure you know which of your dependencies is causing the undesirable transitive dependency. The banned dependencies rule can be specified to fail the BUILD if a troublesome dependency is identified, regardless of path. You'll need to add SPECIFIC exclusions to each path the enforcer detects if the build fails.

Why are exclusions made on a dependency-by-dependency basis instead of at the POM level?

Answer»

This is primarily to ensure that the dependency GRAPH is predictable, as well as to prevent inheritance effects from ELIMINATING a dependent that should not be EXCLUDED. If you have to use the method of last resort and add an exclusion, make sure you know which of your dependencies is causing the undesirable transitive dependency.

The banned dependencies rule can be specified to fail the BUILD if a troublesome dependency is identified, regardless of path. You'll need to add SPECIFIC exclusions to each path the enforcer detects if the build fails.

Discussion

No Comment Found

Related InterviewSolutions

What is the difference between the maven package and the maven install?
How can you skip running the tests for a particular project?
How will you run JUnit tests in parallel with a Maven build?
How is Doxia used by Maven?
What is the use of the Maven Wagon plugin?
Explain Project Aggregation.
Explain the default and the advanced configuration inheritance.
Why are exclusions made on a dependency-by-dependency basis instead of at the POM level?
What is maven-release plugin and how does it work?
Discuss the profile element in settings.xml file.