title: Why should the Gradle Wrapper be committed to VCS?
body: <p><strong>From <a href="https://docs.gradle.org/current/dsl/org.gradle.api.tasks.wrapper.Wrapper.html" rel="noreferrer">Gradle's documentation</a>:</strong></p>
  <blockquote>
  <p>The scripts generated by this task are intended to be committed to
  your version control system. This task also generates a small
  gradle-wrapper.jar bootstrap JAR file and properties file which should
  also be committed to your VCS. The scripts delegates to this JAR.</p>
  </blockquote>
  <p><strong>From:</strong> <a href="https://stackoverflow.com/questions/1273921/what-should-not-be-under-source-control">What should NOT be under source control?</a></p>
  <p>I think <em>generated files</em> should not be in the VCS.</p>
  <p>When are <code>gradlew</code> and <code>gradle/gradle-wrapper.jar</code> needed?</p>
  <p>Why not store a <em>gradle version</em> in the <code>build.gradle</code> file?</p>