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

add missing Kotlin/Groovy snippets for Gradle build scripts

Browse Source
This commit is contained in:
Karol Lewandowski 2022-03-23 12:38:07 +01:00
parent e8eb655752
commit 60fd4e8b09
3 changed files with 38 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
topics/basics/testing_plugins/testing_faq.md
View File

@ -93,12 +93,29 @@ These JAR files are not available in plugin project dependencies, so the Intelli
It's done by setting the `idea.home.path` system property to the absolute path of the checked out sources. It's done by setting the `idea.home.path` system property to the absolute path of the checked out sources.
In projects using Gradle it can be done by providing system property in the `test` task configuration: In projects using Gradle it can be done by providing system property in the `test` task configuration:
<tabs>
<tab title="Kotlin">
```kotlin ```kotlin
test { test {
systemProperty("idea.home.path", "/path/to/intellij-community-sources") systemProperty("idea.home.path", "/path/to/intellij-community-sources")
} }
``` ```
</tab>
<tab title="Groovy">
```groovy
test {
systemProperty "idea.home.path", "/path/to/intellij-community-sources"
}
```
</tab>
</tabs>
The default JDK version used by the test framework depends on the target platform version and is the latest supported version. The default JDK version used by the test framework depends on the target platform version and is the latest supported version.
The easiest way to change the JDK version to the custom is overriding the `LightJavaCodeInsightFixtureTestCase.getProjectDescriptor()` method and using one of the project descriptors predefined in `LightJavaCodeInsightFixtureTestCase`. The easiest way to change the JDK version to the custom is overriding the `LightJavaCodeInsightFixtureTestCase.getProjectDescriptor()` method and using one of the project descriptors predefined in `LightJavaCodeInsightFixtureTestCase`.
If a project descriptor requires more customizations, its `getSdk()` method can use one of the [`IdeaTestUtil.getMockJdk*()`](upsource:///java/testFramework/src/com/intellij/testFramework/IdeaTestUtil.java) methods. If a project descriptor requires more customizations, its `getSdk()` method can use one of the [`IdeaTestUtil.getMockJdk*()`](upsource:///java/testFramework/src/com/intellij/testFramework/IdeaTestUtil.java) methods.
@ -107,13 +124,15 @@ Sometimes testing a JVM language requires adding standard or other libraries to
If a required library is available in the Maven repository, use [`MavenDependencyUtil`](upsource:///java/testFramework/src/com/intellij/testFramework/fixtures/MavenDependencyUtil.java), e.g.: If a required library is available in the Maven repository, use [`MavenDependencyUtil`](upsource:///java/testFramework/src/com/intellij/testFramework/fixtures/MavenDependencyUtil.java), e.g.:
```java ```java
MavenDependencyUtil.addFromMaven(model,"org.jetbrains.kotlin:kotlin-stdlib:1.6.10"); MavenDependencyUtil.addFromMaven(model,
"org.jetbrains.kotlin:kotlin-stdlib:1.6.10");
``` ```
If a required library is an unpublished JAR file, use [`PsiTestUtil.addLibrary()`](upsource:///platform/testFramework/src/com/intellij/testFramework/PsiTestUtil.java) or `addProjectLibrary()` method and the JAR file path, e.g.: If a required library is an unpublished JAR file, use [`PsiTestUtil.addLibrary()`](upsource:///platform/testFramework/src/com/intellij/testFramework/PsiTestUtil.java) or `addProjectLibrary()` method and the JAR file path, e.g.:
```java ```java
PsiTestUtil.addLibrary(model,"kotlin-stdlib",getTestDataPath(),"kotlin-stdlib.jar"); PsiTestUtil.addLibrary(model,
"kotlin-stdlib", getTestDataPath(), "kotlin-stdlib.jar");
``` ```
> If a topic you are interested in is not covered in the above sections, let us know via the "**Was this page helpful?**" feedback form below or [other channels](getting_help.md#problems-with-the-guide). > If a topic you are interested in is not covered in the above sections, let us know via the "**Was this page helpful?**" feedback form below or [other channels](getting_help.md#problems-with-the-guide).

16
topics/products/goland/goland.md
View File

@ -19,6 +19,18 @@ The configuration of targeting GoLand IDE follows the methods described in [Conf
Starting with 2020.2, it's possible to configure `GO` for `intellij.type` in the Gradle build script. Starting with 2020.2, it's possible to configure `GO` for `intellij.type` in the Gradle build script.
<tabs>
<tab title="Kotlin">
```kotlin
intellij {
version.set("2020.3")
type.set("GO")
}
```
</tab>
<tab title="Groovy">
```groovy ```groovy
intellij { intellij {
@ -27,6 +39,10 @@ intellij {
} }
``` ```
</tab>
</tabs>
</tab> </tab>
<tab title="Using Plugin"> <tab title="Using Plugin">

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

@ -29,7 +29,7 @@ intellij {
</tab> </tab>
<tab title="Groovy"> <tab title="Groovy">
```kotlin ```groovy
intellij { intellij {
plugins = ['com.intellij.java'] plugins = ['com.intellij.java']
} }