anchor.diff:  +
   Installs the application into a specified directory.
   
  -`distZip` — link:{groovyDslPath}/org.gradle.api.tasks.bundling.tasks.bundling.Zip.html[Zip]::
  +`distZip` — link:{groovyDslPath}/org.gradle.api.tasks.bundling.Zip.html[Zip]::
   _Depends on_: `jar`, `startScripts`
   +
   Creates a full distribution ZIP archive including runtime libraries and OS specific scripts.
   
  -`distTar` — link:{groovyDslPath}/org.gradle.api.tasks.bundling.tasks.bundling.Tar.html[Tar]::
  +`distTar` — link:{groovyDslPath}/org.gradle.api.tasks.bundling.Tar.html[Tar]::
   _Depends on_: `jar`, `startScripts`
   +
   Creates a full distribution TAR archive including runtime libraries and OS specific scripts.
  
positive.code: +
  Starts the application.
  
  `startScripts` — link:{groovyDslPath}/org.gradle.api.tasks.application.tasks.application.CreateStartScripts.html[CreateStartScripts]::
  _Depends on_: `jar`
  +
  Creates OS specific scripts to run the project as a JVM application.
  
negative.code: include::sample[dir="application/kotlin",files="build.gradle.kts[tags=mainClassName-conf]"]
  ====
  
  You can run the application by executing the `run` task (type: link:{javadocPath}/org/gradle/api/tasks/JavaExec.html[JavaExec]). This will compile the main source set, and launch a new JVM with its classes (along with all runtime dependencies) as the classpath and using the specified main class. You can launch the application in debug mode with `gradle run --debug-jvm` (see link:{javadocPath}/org/gradle/api/tasks/JavaExec.html#setDebug-boolean-[JavaExec.setDebug(boolean)]).
  
  Since Gradle 4.9, the command line arguments can be passed with `--args`. For example, if you want to launch the application with command line arguments `foo --bar`, you can use `gradle run --args="foo --bar"` (see link:{javadocPath}/org/gradle/api/tasks/JavaExec.html#setArgsString-java.lang.String-[JavaExec.setArgsString(java.lang.String)].
  
  