From 6dbb837e30b54f2c4335d6a9a15a75ea4e948c49 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Thu, 7 May 2020 10:21:19 +0200 Subject: [PATCH] build_system.md: cleanup sbt-idea-plugin note --- tutorials/build_system.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tutorials/build_system.md b/tutorials/build_system.md index 910491be1..4237a3080 100644 --- a/tutorials/build_system.md +++ b/tutorials/build_system.md @@ -6,9 +6,7 @@ title: Building Plugins with Gradle The [gradle-intellij-plugin](https://github.com/JetBrains/gradle-intellij-plugin) Gradle plugin is the recommended solution for building IntelliJ plugins. The plugin takes care of the dependencies of your plugin project - both the base IDE and other plugin dependencies. -If a new plugin will be Scala-based, a plugin development workflow [sbt-idea-plugin](https://github.com/JetBrains/sbt-idea-plugin), is available. -The workflow is analogous to the Gradle workflow but tailored to developing IntelliJ Platform plugins in Scala. -JetBrains does not officially support this Scala workflow, and at this time the workflow has only minimal documentation. +> **NOTE** If a new plugin will be Scala-based, a dedicated SBT plugin [sbt-idea-plugin](https://github.com/JetBrains/sbt-idea-plugin) is available. The gradle-intellij-plugin provides tasks to run the IDE with your plugin and to publish your plugin to the [JetBrains plugins repository](/plugin_repository/index.md). To make sure that your plugin is not affected by [API changes](/reference_guide/api_changes_list.md) which may happen between major releases of the platform, you can easily build your plugin against many versions of the base IDE.