From 2a4ffe3c1813804bcc29c940334600b288fb643f Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Tue, 22 Mar 2022 14:23:10 +0100 Subject: [PATCH] rename Gradle build scripts snippet tabs --- topics/basics/plugin_signing.md | 8 ++++---- topics/products/androidstudio/android_studio.md | 6 +++--- topics/products/dev_alternate_products.md | 12 ++++++------ topics/reference_guide/intellij_artifacts.md | 8 ++++---- topics/tutorials/build_system/deployment.md | 8 ++++---- .../tutorials/custom_language_support/annotator.md | 6 +++--- 6 files changed, 24 insertions(+), 24 deletions(-) diff --git a/topics/basics/plugin_signing.md b/topics/basics/plugin_signing.md index 02a5541f4..f218b8cf6 100644 --- a/topics/basics/plugin_signing.md +++ b/topics/basics/plugin_signing.md @@ -79,7 +79,7 @@ Otherwise, it'll be skipped. An example `pluginSigning` configuration may look like: - + ```kotlin signPlugin { @@ -108,7 +108,7 @@ publishPlugin { ``` - + ```groovy signPlugin { @@ -153,7 +153,7 @@ To avoid storing hard-coded values in the project configuration, the most suitab To specify secrets like `PUBLISH_TOKEN` and values required for the `signPlugin` task, modify your Gradle configuration as follows: - + ```kotlin signPlugin { @@ -168,7 +168,7 @@ publishPlugin { ``` - + ```groovy signPlugin { diff --git a/topics/products/androidstudio/android_studio.md b/topics/products/androidstudio/android_studio.md index 381edc3d0..11f41207c 100644 --- a/topics/products/androidstudio/android_studio.md +++ b/topics/products/androidstudio/android_studio.md @@ -53,10 +53,10 @@ Here are the steps to configure the build.gradle file for developin * The best practice is to use the target version of Android Studio as the IDE Development Instance. Set the Development Instance to the (user-specific) absolute path to the target Android Studio application. -The snippet below is an example of configuring the Setup and Running DSLs in a build.gradle specific to developing a plugin targeted at Android Studio. +The snippet below is an example of configuring the Setup and Running DSLs in a Gradle build script specific to developing a plugin targeted at Android Studio. - + ```kotlin intellij { @@ -75,7 +75,7 @@ runIde { ``` - + ```groovy intellij { diff --git a/topics/products/dev_alternate_products.md b/topics/products/dev_alternate_products.md index 36de9deda..253af2185 100644 --- a/topics/products/dev_alternate_products.md +++ b/topics/products/dev_alternate_products.md @@ -49,10 +49,10 @@ Specifying the target as a product-specific `intellij.type` attribute has two ad A build.gradle snippet setting a plugin project to target PyCharm is shown below. The `gradle-intellij-plugin` will fetch the matching build of PyCharm Professional to define the APIs available, and use that build of PyCharm (and associated JetBrains runtime) as the Development Instance. -No additional product-specific configuration needs to be set in build.gradle: +No additional product-specific configuration needs to be set in the Gradle build script: - + ```kotlin intellij { @@ -62,7 +62,7 @@ intellij { ``` - + ```groovy intellij { @@ -131,10 +131,10 @@ The best practice is to modify the `runIde {}` task to use a local installation Set the `runIde.ideDir` attribute to the (user-specific) absolute path of the _targetIDE_ application. The exact path format varies by operating system. -This snippet is an example for configuring the Setup and Running DSLs in a build.gradle specific to developing a plugin for _targetIDE_. +This snippet is an example for configuring the Setup and Running DSLs in a Gradle build script specific to developing a plugin for _targetIDE_. - + ```kotlin intellij { @@ -155,7 +155,7 @@ runIde { ``` - + ```groovy intellij { diff --git a/topics/reference_guide/intellij_artifacts.md b/topics/reference_guide/intellij_artifacts.md index 0797396e6..44758d50b 100644 --- a/topics/reference_guide/intellij_artifacts.md +++ b/topics/reference_guide/intellij_artifacts.md @@ -104,7 +104,7 @@ This code snippet selects the release repository with the first URL, and the rep The second URL is needed because this example selects individual modules. - + ```kotlin repositories { @@ -114,7 +114,7 @@ repositories { ``` - + ```groovy repositories { @@ -131,7 +131,7 @@ repositories { This code snippet specifies the desired module artifacts. - + ```kotlin dependencies { @@ -141,7 +141,7 @@ dependencies { ``` - + ```groovy dependencies { diff --git a/topics/tutorials/build_system/deployment.md b/topics/tutorials/build_system/deployment.md index 0f5c15c37..408ffdee6 100644 --- a/topics/tutorials/build_system/deployment.md +++ b/topics/tutorials/build_system/deployment.md @@ -53,7 +53,7 @@ Now provide the environment variable in the run configuration with which you run To do so, create a Gradle run configuration (if not already done), choose your Gradle project, specify the `publishPlugin` task, and then add the environment variable. - + ```kotlin publishPlugin { @@ -62,7 +62,7 @@ publishPlugin { ``` - + ```groovy publishPlugin { @@ -115,7 +115,7 @@ You may also deploy plugins to a release channel of your choosing, by configurin For example: - + ```kotlin publishPlugin { @@ -124,7 +124,7 @@ publishPlugin { ``` - + ```groovy publishPlugin { diff --git a/topics/tutorials/custom_language_support/annotator.md b/topics/tutorials/custom_language_support/annotator.md index 90a356cd8..1550029e3 100644 --- a/topics/tutorials/custom_language_support/annotator.md +++ b/topics/tutorials/custom_language_support/annotator.md @@ -15,10 +15,10 @@ Classes defined in this step of the tutorial depend on `com.intellij.psi.PsiLite Using `PsiLiteralExpression` [introduces a dependency](plugin_compatibility.md#modules-specific-to-functionality) on `com.intellij.java`. Beginning in version 2019.2, a dependency on Java plugin [must be declared explicitly](https://blog.jetbrains.com/platform/2019/06/java-functionality-extracted-as-a-plugin/). -First, add a dependency on the Java plugin in Gradle build file: +First, add a dependency on the Java plugin in the Gradle build script: - + ```kotlin intellij { @@ -27,7 +27,7 @@ intellij { ``` - + ```kotlin intellij {