- #INTELLIJ IDEA COMMUNITY PLUGINS FOR FREE#
- #INTELLIJ IDEA COMMUNITY PLUGINS ANDROID#
- #INTELLIJ IDEA COMMUNITY PLUGINS PROFESSIONAL#
The Gradle plugin attribute intellij.version is set to be baseIntelliJPlatformVersion.įor API compatibility, the IntelliJ Platform version used in the targetIDE dictates the baseIntelliJPlatformVersion used for developing a plugin. The IntelliJ Platform is defined by a specific build of the IntelliJ IDEA Community Edition.
#INTELLIJ IDEA COMMUNITY PLUGINS ANDROID#
TargetIDE is the (version-specific) IntelliJ Platform-based IDE in which the plugin is intended to run, such as Android Studio or PhpStorm.īaseIntelliJPlatformVersion is the (version-specific) IntelliJ Platform used in the build of the targetIDE.
Understanding the relationship between build numbers is critical when using this approach to project configuration: However, testing the plugin project in the target product itself helps to find such mistakes.Īdditional configuration must be done to match the version of IntelliJ IDEA to the version of the target product. This does have the drawback that APIs not specific to the target product might accidentally be included in the plugin project. In this case, the build script is configured to use IntelliJ IDEA (Community or Ultimate Edition) as the basis for the available APIs. If the Gradle IntelliJ Plugin does not directly support an IntelliJ Platform-based product, the Gradle build script can still be configured to target the desired product. No additional product-specific configuration needs to be set in the Gradle build script:Ĭonfiguring Plugin Projects Using the IntelliJ IDEA Product Attribute
#INTELLIJ IDEA COMMUNITY PLUGINS PROFESSIONAL#
The Gradle IntelliJ Plugin will fetch the matching build of P圜harm Professional to define the APIs available, and use that build of P圜harm (and associated JetBrains Runtime) as the Development Instance. The default IDE Development Instance for running the plugin will be the target product.Ī Gradle build script snippet setting a plugin project to target P圜harm is shown below.
(Unless additional plugin dependencies are specified.) The APIs available to the plugin will be limited to only what is defined in the target product. Specifying the target as a product-specific intellij.type property has two advantages: If the Gradle IntelliJ Plugin supports a target product directly, there will be an intellij.type property defined. Configuring Plugin Projects Using a Product-Specific Attribute To target multiple products (e.g., IntelliJ IDEA and P圜harm) with the same plugin, see Plugin Compatibility with IntelliJ Platform Products page. The best approach then is to configure the project using the IntelliJ IDEA Attribute. NOTE: Not all products have an intellij.type property defined by the Gradle IntelliJ Plugin, for example, Android Studio and PhpStorm. Configuration using an intellij.type property is explained in the Configuring Plugin Projects Using a Product-Specific Attribute section below. The best practice is to use the intellij.type property to specify the target product. Configuring Gradle Build Script to Target Products Other Than IntelliJ IDEA The plugin.xml file is modified to declare the plugin's dependency on modules or libraries. The Gradle build script is modified to specify the target product, determining the APIs available during development. Modifications are needed to the skeleton project's Gradle build script and plugin.xml files, as described below, and on the individual product pages in Part VIII - Product Specific.
The tutorial produces a skeleton Gradle project suitable to use as a starting point. To create a new Gradle plugin project, follow the tutorial on the Creating a Plugin Gradle Project page.
#INTELLIJ IDEA COMMUNITY PLUGINS FOR FREE#
Qualifying Open Source projects can apply for free licenses of JetBrains products. Details particular to an IntelliJ Platform-based product are described on the individual product pages in Part VIII - Product Specific.Īll the Gradle configuration attributes described here are discussed in-depth on the Configuring Gradle IntelliJ Plugin and the Gradle IntelliJ Plugin. Project configuration attributes common to projects targeting products other than IntelliJ IDEA are described on this page. Once completed, the plugins can be packaged and distributed at JetBrains Marketplace. They can be written in Kotlin or Java, or a mix of both. Such plugins are developed much like plugin projects that target IntelliJ IDEA.
Plugin projects can target IDEs other than IntelliJ IDEA, as long as the products are based on the IntelliJ Platform. Plugins Targeting IntelliJ Platform-Based IDEs
0 kommentar(er)
