Getting Started with Gradle
Gradle is the preferred solution for creating IntelliJ Platform plugins. The IntelliJ IDEA Ultimate and Community editions bundle the necessary plugins to support Gradle-based development. These IntelliJ IDEA plugins are Gradle and Plugin DevKit, which are enabled by default. To verify these plugins are installed and enabled, see the help section about Managing Plugins.
Creating a Gradle-Based IntelliJ Platform Plugin with New Project Wizard
Creating new Gradle-based IntelliJ Platform plugin projects is performed using the New Project Wizard. The Wizard creates all the necessary project files based on a few template inputs.
Before creating a new Gradle project, familiarize yourself with the help topic Creating a new Gradle project, which is a tutorial for creating general Gradle projects in IntelliJ IDEA. This page emphasizes the steps in the process of creating IntelliJ Platform plugin projects that are Gradle-based. Additionally, screencast Working with Gradle in IntelliJ IDEA offers a thorough introduction.
Launch the New Project Wizard. It guides you through the Gradle project creation process with two screens.
New Project Configuration Screen
On the first screen, the type of project is configured:
From the project type pane on the left, choose Gradle.
Specify the Project SDK based on the Java 8 JDK. This SDK will be the default JRE used to run Gradle, and the JDK version used to compile the plugin Java sources.
In the Additional Libraries and Frameworks panel, select Java and IntelliJ Platform Plugin. These settings will be used for the remainder of this tutorial.
To include support for the Kotlin language in the plugin, check the Kotlin/JVM box (circled in green below). This option can be selected with or without the Java language. See Kotlin for Plugin Developers for more information.
To create the build.gradle file as a Kotlin build script (build.gradle.kts) rather than Groovy, check the Kotlin DSL build script box (circled in magenta below).
Then click Next:
Project Naming/Artifact Coordinates Screen
GroupId is typically a Java package name, and it is used for the Gradle property
project.groupvalue in the project's build.gradle file. For this example, enter
ArtifactId is the default name of the project JAR file (without version). It is also used for the Gradle property
rootProject.namevalue in the project's settings.gradle file. For this example, enter
Version is used for the Gradle property
project.versionvalue in the build.gradle file. For this example, enter
The Name field is synced automatically with the specified ArtifactId.
Specify the path for the new project in Location and click Finish to continue and generate the project.
Components of a Wizard-Generated Gradle IntelliJ Platform Plugin
For the example
my_gradle_plugin, the New Project Wizard creates the following directory content:
The default IntelliJ Platform build.gradle file (see next paragraph).
The Gradle Wrapper files, and in particular the gradle-wrapper.properties file, which specifies the version of Gradle to be used to build the plugin. If needed, the IntelliJ IDEA Gradle plugin downloads the version of Gradle specified in this file.
The settings.gradle file, containing a definition of the
my_gradle_plugin project build.gradle file:
- Two plugins to Gradle are explicitly declared:
The GroupId from the Wizard Project Naming/Artifact Coordinates Screen is the
The Version from the Wizard Project Naming/Artifact Coordinates Screen is the
sourceCompatibilityline is injected to enforce using Java 8 JDK to compile Java sources.
The only comment in the file is a link to the README.md for the gradle-intellij-plugin, which is a reference for its configuration DSL.
The value of the Setup DSL attribute
intellij.versionspecifies the version of the IntelliJ Platform to be used to build the plugin. It defaults to the version of IntelliJ IDEA that was used to run the New Project Wizard.
The value of the Patching DSL attribute
patchPluginXml.changeNotesis set to a place holder text.
Plugin Gradle Properties and Plugin Configuration File Elements
The Gradle properties
project.group will not, in general, match the respective plugin configuration file plugin.xml elements
<id>. There is no IntelliJ Platform-related reason they should as they serve different functions.
<name> element (used as the plugin's display name) is often the same as
rootProject.name, but it can be more explanatory.
<id> value must be a unique identifier over all plugins, typically a concatenation of the specified GroupId and ArtifactId. Please note that it is impossible to change the
<id> of a published plugin without losing automatic updates for existing installations.
Adding Gradle Support to an Existing DevKit-Based IntelliJ Platform Plugin
Converting a DevKit-based plugin project to a Gradle-based plugin project can be done using the New Project Wizard to create a Gradle-based project around the existing DevKit-based project:
Ensure the directory containing the DevKit-based IntelliJ Platform plugin project can be fully recovered if necessary.
- Delete all the artifacts of the DevKit-based project:
Arrange the existing source files within the project directory in the Gradle SourceSet format.
Use the New Project Wizard as though creating a new Gradle project from scratch.
- On the Project Naming/Artifact Coordinates Screen set the values to:
GroupId to the existing package in the initial source set.
ArtifactId to the name of the existing plugin.
Version to the same as the existing plugin.
Name to the name of the existing plugin. (It should be pre-filled from the ArtifactId)
Set the Location to the directory of the existing plugin.
Click Finish to create the new Gradle-based plugin.
Running a Simple Gradle-Based IntelliJ Platform Plugin
Gradle projects are run from the IDE's Gradle Tool window.
Adding Code to the Project
Executing the Plugin
Open the Gradle tool window and search for the runIde task:
If it’s not in the list, hit the Refresh button at the top of the Gradle tool window.
Double-click on the runIde task to execute it. See the IntelliJ IDEA help for more information about Working with Gradle tasks.
To debug your plugin in a standalone IDE instance, please see How to Debug Your Own IntelliJ IDEA Instance blog post.