If you don’t have much time then stick to the currentīuild of IntelliJ, e.g. UsersĪre expected to upgrade to newer versions more quickly. Is usually a lot easier than to extend your plugin’s compatibility to older builds.Īt the time when the 145.x build was released JetBrains switched to a subscription based licensing model. You may choose to drop support for older versions in the future, supporting newer versions To spend to support older versions of the products. Your choice will depend on your target audience, the features you would like to implement and the time you’d like The details of the naming schema are documented in the developer wiki.
JetBrains releases about 3 new major versions of its products each year. Choose your target environment IntelliJ major buildĪt first you should choose the minimum version of the platform you would like to support. IntelliJ comes in many different editions and versions.
Make sure to enable the plugin Plugin DevKit to get useful actions and inspections which support you to work on your pluign. Use IntelliJ, of course! The Community edition provides all you need to get started. For example, JavaScript support is not available in Community editions of IntelliJ or P圜harm but is part of JetBrains' commercial offerings. Some functionality is limited to certain products, though. Many of IntelliJ’s featuers are available in all of these products and may be used or extended by your plugin. Please note: ReSharper and ReSharper C++ are not based on the IntelliJ platform and are therefore not compatible with plugins targeting this environment. This includes IntelliJ IDEA Ultimate and Community, WebStorm, PHPStorm, P圜harm Community / Pro / Edu, CLion, DataGrip, AppCode and Gogland. When I’m referring to IntelliJ then the other products of the same family are also meant, of course. It is assumed that you use IntelliJ IDEA Community or Ultimate as Source code won’t be explained unless it’s related to IntelliJ. I assume general knowledge of Java, Swing, JUnit, XML and Gradle and also expect that you (if you want to add support for a new language) know about lexers, parser grammars and the related concepts. This post is intended for experienced Java developers. I’ll update this page from time to time to make sure that it’s up-to-date and as helpful as possible. Please let me know if you miss information about certain areas of the development process. It’s a great idea! This post helps you to get started and to learn about best practices to work on it.Īfter reading this article (and the further resources it links to) you should be able to get started with the development You probably are planning to build and deploy your own plugin. Product itself may be disabled, but can not be uninstalled. Plugins can be installed, uninstalled, enabled and disabled by the user. Much of the built-in functionality is already implemented with the help of plugins. With the help of plugins the products can be enhanced with things like new languages, additional code completion, expanded documentation content, support for new frameworks and the like. Products based on the IntelliJ platform are expandable by plugins.
0 kommentar(er)
