The libraries are Java, and as such platform independent. From there, we can point to the libraries and subsequently compile and test the plugin. The plan is as follows: download the Linux version of IntelliJ IDEA, and extract it in a predefined location. Since the IDEA libraries are not available via Maven repos, an IntelliJ IDEA Community Edition download is probably the best option to get a hold of the libraries. My plugin code adheres to the default Gradle project structure.įirst thing to do is to get a hold of the IntelliJ IDEA libraries in an automated way. Update: I ran into some issues with forms and language code generation and added some updates at the end of this post. The plugin module files are only slightly different from your average project. The SDK can point to your IntelliJ installation. If you want to create a language plugin you might want to install Grammar-Kit too. The Plugin DevKit plugins need to be installed. First of all you’ll need IntelliJ IDEA.In order to build and test a plugin, the following needs to be in place: Tomasz Dziurko put me in the right direction. IDE configurations can not be generated from the build script.the code can not be compiled and tested on a CI environment.it can not be compiled and packaged from the command line.Unless you’re using TeamCity as your CI tool, you’re out of luck.įor me it makes no sense writing code if: The JetBrains folks simply have not catered for that. It looked hard to create a build script to do the actual plugin compilation and packaging from a build script. Plugin development all relies on IDE features. Recently I dove into the world of plugin development for IntelliJ IDEA and was unhappily surprised. For a few years already, IntelliJ IDEA has been my IDE of choice.

Intellij install plugin