If the project uses DevKit, add the JARs of the plugin on which the project depends to the Classpath of the IntelliJ Platform SDK.ĭo not add the plugin JARs as a library: this will fail at runtime because the IntelliJ Platform will load two separate copies of the dependency plugin classes. Project Setupĭepending on the chosen development workflow (Gradle or DevKit), one of the two following steps is necessary.Įxisting DevKit-based projects can be converted to use Gradle setup where managing dependencies is fully automated.
Pycharm please specify a different sdk name install#
If the plugin is not bundled with the target IDE, run the (sandbox) IDE Development Instance of your target IDE and install the plugin there. Open detail page for the desired version, displaying the Compatibility Range and Plugin IDįor bundled and non-public plugins, locate the plugin's main JAR file containing META-INF/plugin.xml descriptor with tag (or if not specified). Locating Plugin ID and Preparing SandboxĪ compatible version must be chosen carefully according to the plugin's compatibility.įor plugins published on JetBrains Plugins Repository If NoClassDefFoundError occurs at runtime, it means that either Step 3 was omitted or loading the plugin dependency failed (please check log files from Development Instance).ġ. To express dependencies on classes from other plugins or modules, perform the following three required steps detailed below on this page: It is impossible to specify the minimum/maximum version for the dependent plugin. For more information about dependencies on the IntelliJ Platform modules, see Part II of this document: Plugin Compatibility with IntelliJ Platform Products. This document describes the syntax for declaring plugin dependencies and optional plugin dependencies. A plugin may depend on classes from other plugins, either bundled, third-party, or by the same author.