The project we've been working on this year together with the Marketplace team is finally ready for the first public release! IntelliJ Platform Explorer is a web tool integrated within the Marketplace platform. It helps IntelliJ Platform plugin developers examine implementations of the Extension Points available in public GitHub repositories. Backstory When working on IntelliJ Platform plugins as a third-party developer, it’s essential that you examine the source code of the IntelliJ Community repository and other existing plugins hosted on GitHub. Analyzing existing Extension Point examples

Want to create a plugin for IntelliJ Platform but tired of reading the documentation? Join our webinar on Wednesday, December 16, 2020 at 17:00 CET / 16:00 UTC / 11:00 EST for all the information you need to get started writing plugins. We will be covering: IntelliJ Platform SDK, Useful resources for planning, developing, and deploying plugins with the IntelliJ Platform SDK, IntelliJ Platform Plugin Template, Free and paid plugins, and how to customize your plugin page and make it stand out in JetBrains Marketplace. Register to save the date, get a calendar invite, and a reminder 30 minut

As you may already know, Apple deprecated the OpenGL rendering library in macOS Mojave and provided the Metal framework as a replacement. Metal better reflects the shift in CPU/GPU performance that has happened over the last 20 years. So, with proper implementation, apps that are based on Metal perform better and consume less energy than the old OpenGL ones. What does this mean for our products? Our Java-based IDEs use the Swing UI toolkit, which renders using the Java 2D API. Internally, Java 2D uses platform APIs to present the result of rendering. Starting with JDK7, the rendering subsystem

The upcoming 2020.3 releases will include internal changes related to a significant redesign of the representation of project models in the IntelliJ Platform. This shouldn’t affect any plugins using the IntelliJ API properly and which don’t access internal classes. However, we want to give an overview of the changes and offer some insight into the reasons behind them. There are several problems with the approach that has been used to represent the project model (configuration of modules, libraries, facet, artifacts, etc.) in the IntelliJ Platform for more than 15 years. First, different projec

IntelliJ Platform Plugin Template IntelliJ Platform Plugin Template, our GitHub-based repository, provides a pure boilerplate to make it easier to create a new plugin project. It delivers curated solutions for handling the changelog and supporting Kotlin and Java sources, and provides preconfigured GitHub Actions that take care of plugin quality and deployment. Learn more here: IntelliJ Platform Plugin Template. SDK Docs content updates We’ve added several new reference pages and tutorials to our SDK Docs, including: Settings Disposer and Disposable Marketing All plugin code samples are als

The source code of the IntelliJ project was recently migrated to Java 11. We still have some modules which are compiled to be compatible with older Java versions to support running users’ projects under these versions. However most of the platform and plugin modules use Java 11 now, and the upcoming 2020.3 versions of all IntelliJ-based IDEs will require Java 11 to start. What does it mean for you? If you develop a plugin, you can use new language features and APIs from Java 11, but only if the since-build attribute in plugin.xml is set to 203. If your plugin distribution needs to run on multi

Today we are speaking with Scott McKinny of Manifold Systems (scott@manifold.systems,) the author of the Manifold plugin for IntelliJ Platform-based IDEs. As a Java compiler plugin, Manifold adds new capabilities directly and seamlessly to the Java language such as type-safe metaprogramming, extension methods, operator overloading, and more. Welcome to the JetBrains Platform Blog, Scott. Before we discuss the plugin, would you tell us a bit about yourself and your background? Most of my programming experience is rooted in tooling. It goes way back to my employment with Borland beginning in 199

We have implemented a plugin-signing mechanism and are going to introduce it step by step.

We want to give you an update regarding the status of the JavaFX runtime and JCEF in the IntelliJ Platform. TL;DR Starting with version 2020.2 of the IDE, which will be released at the end of July 2020, we are no longer bundling JavaFX with the default JetBrains Runtime. As an alternative to these APIs, we now provide integration with JCEF, which is a Java port of the CEF framework for embedding Chromium-based browsers in applications using Swing. If you’re thinking about developing a new plugin or adding new features to an existing plugin, JCEF can offer you a new easy way to display web

Just over a year ago, we announced the launch of paid plugins on the JetBrains Marketplace. Today we want to highlight some of the major updates we’ve made to paid plugin functionality on the Marketplace and in our IDEs during the first year of the Marketplace’s operation.

TL;DR We are going to use organizations in search instead of the vendor field from the plugin descriptor. Several weeks ago we introduced Organizations. One of the reasons we implemented them was to simplify plugin search for end users. From now on, we are going to use organizations in the search index instead of the vendor field from the plugin descriptor. (more…)

TL;DR We have added the ability to consolidate authors and their plugins in an Organization in Marketplace. There are almost 5,000 plugins in our Plugin repository, including over 20 paid plugins. These plugins are created by both individual users and companies. To increase the credibility of plugins, simplify the search process for end-users, and facilitate the support of plugins, we’ve added a new entity to the Marketplace called "Organization". An organization comprises authors and their plugins. It provides users with information such as the organization’s website, email, and ad