hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-28 09:17:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

rename Gradle build scripts snippet tabs

Browse Source
This commit is contained in:
Karol Lewandowski 2022-03-22 14:23:10 +01:00
parent 6526f21b17
commit 2a4ffe3c18
6 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
topics/basics/plugin_signing.md
View File

@ -79,7 +79,7 @@ Otherwise, it'll be skipped.
An example `pluginSigning` configuration may look like: An example `pluginSigning` configuration may look like:
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
signPlugin { signPlugin {
@ -108,7 +108,7 @@ publishPlugin {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
signPlugin { 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: To specify secrets like `PUBLISH_TOKEN` and values required for the `signPlugin` task, modify your Gradle configuration as follows:
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
signPlugin { signPlugin {
@ -168,7 +168,7 @@ publishPlugin {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
signPlugin { signPlugin {

6
topics/products/androidstudio/android_studio.md
View File

@ -53,10 +53,10 @@ Here are the steps to configure the <path>build.gradle</path> file for developin
* The best practice is to use the target version of Android Studio as the IDE Development Instance. * 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. 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 <path>build.gradle</path> 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.
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
intellij { intellij {
@ -75,7 +75,7 @@ runIde {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
intellij { intellij {

12
topics/products/dev_alternate_products.md
View File

@ -49,10 +49,10 @@ Specifying the target as a product-specific `intellij.type` attribute has two ad
A <path>build.gradle</path> snippet setting a plugin project to target PyCharm is shown below. A <path>build.gradle</path> 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. 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 <path>build.gradle</path>: No additional product-specific configuration needs to be set in the Gradle build script:
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
intellij { intellij {
@ -62,7 +62,7 @@ intellij {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
intellij { 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. Set the `runIde.ideDir` attribute to the (user-specific) absolute path of the _targetIDE_ application.
The exact path format varies by operating system. The exact path format varies by operating system.
This snippet is an example for configuring the Setup and Running DSLs in a <path>build.gradle</path> 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_.
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
intellij { intellij {
@ -155,7 +155,7 @@ runIde {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
intellij { intellij {

8
topics/reference_guide/intellij_artifacts.md
View File

@ -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. The second URL is needed because this example selects individual modules.
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
repositories { repositories {
@ -114,7 +114,7 @@ repositories {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
repositories { repositories {
@ -131,7 +131,7 @@ repositories {
This code snippet specifies the desired module artifacts. This code snippet specifies the desired module artifacts.
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
dependencies { dependencies {
@ -141,7 +141,7 @@ dependencies {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
dependencies { dependencies {

8
topics/tutorials/build_system/deployment.md
View File

@ -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. 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.
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
publishPlugin { publishPlugin {
@ -62,7 +62,7 @@ publishPlugin {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
publishPlugin { publishPlugin {
@ -115,7 +115,7 @@ You may also deploy plugins to a release channel of your choosing, by configurin
For example: For example:
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
publishPlugin { publishPlugin {
@ -124,7 +124,7 @@ publishPlugin {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```groovy ```groovy
publishPlugin { publishPlugin {

6
topics/tutorials/custom_language_support/annotator.md
View File

@ -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`. 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/). 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:
<tabs> <tabs>
<tab title="Gradle Kotlin DSL"> <tab title="Kotlin">
```kotlin ```kotlin
intellij { intellij {
@ -27,7 +27,7 @@ intellij {
``` ```
</tab> </tab>
<tab title="Gradle"> <tab title="Groovy">
```kotlin ```kotlin
intellij { intellij {