#Intellij plugins how to#
Once I knew what to look for, this post helped me out: How to manage development life cycle of IntelliJ plugins with Maven, along with this build script. This task can be loaded in Gradle and used as a last step of compilation. For instrumentation an Ant task is available. Those classes are used as “helpers” for the form after instrumentation. Check out this commit to see what has to be added. Including more files in the plugin was easy enough. This difference is only obvious once you compare the plugin built by IntelliJ with the one built by Gradle:
#Intellij plugins update#
Update 1: Formsįor an IntelliJ plugin to use forms it appeared some extra work has to be performed. Have a look at my idea-clock plugin for a working example.
Logger.warn " Make sure you have it configured IntelliJ before opening the project!" Task extractIdeaSdk(type: Copy, dependsOn: ) ’." IntelliJ IDEA can still run on a Java 6 JRE, so we need to take that into account. TestCompile ‘org.mockito:mockito-core:1.10.19’ IdeaSdk fileTree(dir: ‘lib/sdk/’, include: ) Pick the Linux version, as it is a tar.gz we can simply extractĭef IDEA_SDK_NAME = ‘IntelliJ IDEA Community Edition IC-139.1603.1’īundle // dependencies bundled with the plugin The following code snippet caters for this: I picked the Linux version since it has a nice, simple file structure. 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.
#Intellij plugins install#
If you want to create a language plugin you might want to install Grammar-Kit too. The Plugin DevKit plugins need to be installed.
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.
0 kommentar(er)
