Build Tools · interview question
Why do teams use a locking mechanism for dependencies in a Gradle project in production code?
Multiple choiceHardchapter-10-curatedpremiumbuild-toolsdependency-management
Answer and explanation
Correct answer
B. To ensure reproducible builds by fixing dependency versions
Why
The primary purpose of using a locking mechanism in Gradle is to ensure reproducible builds by locking dependency versions. This prevents unexpected changes in dependency versions that could otherwise occur due to changes in external repositories.
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?