Gradle Dependency Resolution Language Collocations
Practise the standard verbs for resolving and auditing Gradle dependencies.
0 / 5 completed
1 / 5
Fill in: 'We ___ a dependency version explicitly in the build file when two transitive dependencies disagree, rather than letting Gradle's resolution strategy pick one somewhat arbitrarily.'
We 'pin a version' — the standard, established collocation for forcing a specific dependency version during resolution. The other options aren't the recognised term here.
2 / 5
Fill in: 'Leaving a version conflict between two transitive dependencies unresolved can ___ the build silently picking whichever version happens to be declared last.'
We say an unresolved conflict will 'leave' the build silently picking a version — the standard, natural collocation for the resulting ambiguity. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the full dependency tree before a major library upgrade, so a transitive version bump elsewhere in the graph doesn't surprise us after the build already breaks.'
We 'inspect' a dependency tree — the standard, simple collocation for examining the resolved graph of a build. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ dependency locking for reproducible builds, so the exact same resolved versions are used in CI today as they will be again next month.'
We 'enable locking' — the standard, established Gradle collocation for turning on a feature that freezes resolved versions. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ every dependency's licence and known vulnerabilities as part of resolution, rather than assuming a transitive library pulled in incidentally is automatically safe to ship.'
We 'audit' a dependency — the standard, simple collocation for periodically reviewing a library before trusting it in a build. The other options are less idiomatic here.