> Now “obviously” the answer is that we should have pegged the version of gradle required to use the script My first step with either gradle or maven is to ins

> Now “obviously” the answer is that we should have pegged the version of gradle required to use the script My first step with either gradle or maven is to install the wrapper generator, which has this effect. After adding the wrapper you invoke it via ./gradlew or ./mvnw in the project directory. The version of gradle or maven is then pinned until manually updated. It’s not perfect - especially in terms of IDE support - but it’s crucial for keeping your CLI builds consistent across team members and in automation. gradle wrapper: https://docs.gradle.org/current/userguide/gradle_wrapper.html https://docs.gradle.org/current/userguide/gradle_wrapper.htm... maven wrapper: https://github.com/takari/maven-wrapper https://github.com/takari/maven-wrapper