anchor.diff:  We will show you in this section how to do that for the Android Plugin for Gradle.
   
   [NOTE]
  -When publishing plugins, please use Gradle's built-in link:{user-manual}java_gradle_plugin.html[Java Gradle Plugin] Plugin. It automates the publication of the metadata necessary to make your plugins usable with the `plugins {}` block.
  +When publishing plugins, please use Gradle's built-in <<java_gradle_plugin#, Java Gradle Plugin>> Plugin. It automates the publication of the metadata necessary to make your plugins usable with the `plugins {}` block.
   
   The goal is to instruct your build on how to map the `com.android.application` plugin identifier to a resolvable artifact.
   This is done in two steps:
  
positive.code: 
  All `gradle.kts` script has implicit imports comprised of:
  
  * the link:{user-manual}writing_build_scripts.html#script-default-imports[default Gradle API imports],
  * the Gradle Kotlin DSL API: `org.gradle.kotlin.dsl.*`.
  
  
  
negative.code: 
  To use the Kotlin DSL, simply name your files `build.gradle.kts` instead of `build.gradle`.
  
  The <<build_lifecycle#sec:settings_file, settings file>>, `settings.gradle`, can also be renamed `settings.gradle.kts`.
  
  In a multi-project build, you can have some modules using the Groovy DSL (with `build.gradle`) and others using the Kotlin DSL (with `build.gradle.kts`).
  
  On top of that, apply the following conventions for better IDE support:
  
  * Name scripts that are applied to `Settings` according to the pattern `*.settings.gradle.kts`,
  * Name <<init_scripts#, init scripts>> according to the pattern `*.init.gradle.kts`.
  
  [TIP]
  .Precompiled script plugins
  