Build Tools · interview question
What is 'dependency hell', and how can it be avoided in a Gradle project?
Multiple choiceHardchapter-10-curatedpremiumbuild-toolsdependency-management
Answer and explanation
Correct answer
A. Conflicts due to version mismatches; resolved by using dependency constraints
Why
Dependency hell refers to conflicts and issues that arise from managing many dependencies, especially when they depend on different versions of the same library. In Gradle, it can be mitigated by using dependency constraints to enforce compatible versions.
Test yourself on Build Tools
A free test with instant, explained results. No account needed.
More Build Tools questions
- In a Maven project, where do you declare a dependency for a new library you want to use?
- Which Maven command would you use to ensure that the project is cleaned and rebuilt, including tests?
- When using Maven, which phase is responsible for verifying the quality of the code by running integration tests?
- In a Maven project, how are dependencies typically fetched?
- How does Maven resolve dependencies that are not present in the local repository?
- Which of the following is a primary benefit of using Gradle over Ant for building Java projects?