Deprecation Notice: Login/Password Authentication in the API Replaced with Token-based Authentication

We would like you to be informed that the login/password authentication method previously available in the API has been replaced with token-based authentication. This will help improve the security of your plugins. We ask that you switch to the new auth method as soon as possible.

The JetBrains Hub authentication policies have changed as we’ve introduced mandatory two-factor authentication. For this reason, the login/password option for publishing your plugins to via the API will stop working on August 26, 2019.

If you are using plugin-repository-rest-client or gradle-intellij-plugin, you should pass the token instead of both username and password.

Should you have any questions, feel free to write to us at or leave a comment to this blog post.

Happy Developing!
The JetBrains Marketplace Team

Posted in IntelliJ Platform, Plugin Repository, ReSharper Platform, TeamCity Platform | Tagged , , , | Leave a comment

JetBrains Marketplace is Live

Last September, we announced the start of the JetBrains Marketplace Early Access Program, and we are very grateful to the 100+ individual plugin developers and companies who participated in this EAP and shared their feedback with the Marketplace team. It was a fantastic journey for all of us, and it definitely proved that we have a community of plugin developers for JetBrains tools who are truly awesome!

JetBrains Marketplace platform is an evolutionary new step for the plugins repository which turns it into a marketplace for third-party plugin developers to sell their plugins and take advantage of an out-of-the-box licensing and billing solution provided by JetBrains.

It is time to move on and remove the EAP flag from our project page. We are pleased to announce that starting today, we have 10 third-party plugins proudly being sold and licensed via the JetBrains Marketplace. You can apply to have your own paid plugin be a part of this journey here.


Continue reading

Posted in General, IntelliJ Platform, Plugin Repository | Tagged , , , , , | Leave a comment

Java functionality extracted as a plugin

In the latest EAP build of IntelliJ IDEA 2019.2 we’ve extracted Java functionality into a separate plugin. This separates the Java implementation from the “platform” part of IntelliJ IDEA and introduces some flexibility for the future. For example, we could include Java functionality as a plugin to other products, and other plugins such as Gradle can now take optional dependencies on Java, and still work if Java isn’t available.

The new plugin is not visible in Settings | Plugins and cannot be switched off, so there should be no impact on end users. However, if you’re writing a plugin for IntelliJ IDEA you may need to make some small changes to continue working correctly.

Firstly, if your plugin depends on the Java part of the IntelliJ API, you will need to declare this dependency in your plugin.xml file, by adding the following line:

You might have this line in your  plugin.xml already, as this is the recommended way of declaring a dependency on the Java functionality, even for earlier versions of IntelliJ IDEA. However, it is now required, to ensure that your plugin can access classes from the Java plugin at runtime. See the Plugin Compatibility with IntelliJ Platform Products page for more details on dependencies.

Secondly, if you’re developing a plugin using gradle-intellij-plugin, you need to tell Gradle about the Java plugin. Add the following to build.gradle in order to include classes from the Java plugin into the compilation classpath, and tell the IDE to load the plugin at runtime:

Please let us know if you have any issues.

Posted in IntelliJ Platform | Tagged , , , | 6 Comments

Creating Custom Themes for IntelliJ Platform IDEs

Beginning with the 2019.1 release, Custom UI Themes can be provided by 3rd party authors to customize the whole Look and Feel of the IDE.


Customization is done by packaging a Theme descriptor file (JSON format) as a plugin. Most themes will change the colors of the UI, but replacing icons, changing the appearance of borders, and bundling editor schemes are also possible. By the way, the bundled “ High contrast” theme uses the same mechanism.

After uploading the Custom UI Theme plugin to the JetBrains Plugin Repository (, it can easily be installed right from the IDE’s plugin manager and activated via Preferences | Appearance & Behavior | Appearance “Theme” combo box.


Get started today by following the detailed tutorial we’ve added to the IntelliJ Platform SDK docs that will walk you through the process of creating a custom Theme. As a reference, you can also take peek at the provided sample Theme plugin.

Posted in IntelliJ Platform | 19 Comments

JetBrains Marketplace service to replace ReSharper gallery on January 30th, 2019

We would like to inform all the ReSharper Platform plugin developers that the ReSharper gallery server is being retired and will be soon turned off. All the plugins from the ReSharper gallery will be migrated to the JetBrains Marketplace. All new plugins and plugin updates should be uploaded to there after the migration is finished.


The migration will be performed on January 30th, 2019. As a result of this change, any existing NuGet API keys will no longer be valid. A new token must be obtained from JetBrains Hub as described in the documentation. Also, you need login at JetBrains Marketplace after January 30th, to verify that your plugins were migrated and you are able to manage them.

We have already sent the e-mail notification to all the developers with plugins published in the ReSharper Gallery, and will post the update here as soon as the migration is successfully completed.

If you have any issues with recovering ownership of your plugins or any other questions, please contact us.

Develop with pleasure,
JetBrains Marketplace Team

Posted in Plugin Repository, ReSharper Platform | Tagged , , | 2 Comments

Cleaning up tags on GitHub

Since we started development on IDEA, every nightly build of each IntelliJ-based IDE was tagged in the intellij-community repository on GitHub. After 18 years of development and having 10 products, we now have more than 68,000 tags in the repository! This many tags causes performance issues with git, in particular, every git fetch is very slow.

To improve the experience of working with the intellij-community repository, both for us and for our contributors, we have removed these tags. We’re currently deciding on whether they are needed on GitHub and what our tagging strategy will be going forward.

If you need a specific tag that isn’t available in the  intellij-community repo on GitHub (e.g. for an EAP, a release version or a different product) you can still find it in the git mirror on which will be keeping all of the tags. For convenience, a couple of scripts were added to the project to work with the mirror – one to fetch a single tag by name, and another to list all tags.

Posted in IntelliJ Platform | Tagged , | Leave a comment

Updated guidance for module JARs in IntelliJ based IDEs

When building an IntelliJ based IDE, we’ve historically packed class files from implementation modules into a single big JAR. For example, for IntelliJ IDEA Ultimate this was idea.jar. However most of the classes in that JAR were IntelliJ Platform classes which are included in all IntelliJ-based IDEs. In IntelliJ IDEA 2018.1 we extracted such common classes to a separate platform-impl.jar file. Similarly, we extracted common platform API classes from openapi.jar to  platform-api.jar. This can help to decrease build and startup time for the IDE, and also makes layout of different IDEs more consistent.

Now we’re recommending that you do the same for your own IntelliJ-based IDEs. The change is rather simple, when listing the modules using the ProductModulesLayout class, you should now list only your product specific API and implementation modules, using the new  productApiModules and productImplementationModules properties (note the prefix is product!).

The platfromApiModules and platformImplementationModules properties you would have been using previously are now deprecated, and should be left unassigned, in which case the default behaviour is to pack the modules listed in CommunityRepositoryModules#PLATFORM_API_MODULES into platform-api.jar, and CommunityRepositoryModules#PLATFORM_IMPLEMENTATION_MODULES into platform-imp.jar. You can read more details in the javadocs for ProductModulesLayout.

You can see how straightforward the change is by taking a look at how it was done for PyCharm Edu in this commit.


Posted in IntelliJ Platform | Tagged , , | Leave a comment

Introducing JetBrains Marketplace

Today we are delighted to share something with you which has been in the works for quite some time and has come about because of earlier requests from some of you. We are also seeing a growing interest in this opportunity from IntelliJ Platform plugin developers.

Meet JetBrains Marketplace, a new platform and an evolution of the plugins repository which turns it into a marketplace for third-party plugin developers to sell their plugins and take advantage of an out-of-the-box licensing and billing solution provided by JetBrains.


The Early Access Program is already available, and we are ready to start the technical testing of a few third-party plugins that are ready to switch to the Marketplace in the nearest future.

Marketplace provides:

  • Out-of-the-box software licensing solution
    Integrated with the JetBrains infrastructure, our licensing solution provides your plugins with the same level of licensing support that our JetBrains products already enjoy. Things like generation of licenses for end-users, support for evaluation licenses, centralized license administration, and management via JetBrains Account, as well as an on-premises license server, licenses protection, in-product licensing module, and more, are all taken care of.
  • Billing and sales infrastructure
    With JetBrains Marketplace, third-party plugin vendors can outsource their entire billing and sales operations to JetBrains, and we will take care of the checkout and payment processing, quotes, invoices, refunds, community programs, discounts, and even sales support for your plugins. In addition, we will utilize our extensive reseller network to make plugins available for purchase via the JetBrains distribution network (which is very important for some markets where direct sales possibilities are limited).
  • Marketing and sales support
    Through the Marketplace, you have the opportunity to promote your plugin to millions of people that use JetBrains products. Our team will be working together with paid plugins vendors on the Marketplace to make sure that the plugin is well suited to the target audience, and we’ll assist you with positioning, promotion, and various marketing and sales activities beneficial to our end-users and plugin vendors.

The Marketplace is now available for IntelliJ IDEA Ultimate, AppCode, CLion, DataGrip, GoLand, PhpStorm, PyCharm Professional, Rider, RubyMine, and WebStorm.

Support for Community Editions / Educational Editions of IntelliJ IDEA-based IDEs, as well as other JetBrains tools (such as .NET and Team Tools), will come later.

Similar to other marketplaces and app stores, we will apply a revenue-sharing model to the JetBrains Marketplace. This means that JetBrains will take a moderate commission from all plugin sales made via the Marketplace to make sure that the model is sustainable and we are able to re-invest into the plugin development ecosystem in the future.

For the full terms and conditions of the Marketplace and more details on the technical solution, we invite you to apply to the already ongoing Marketplace Early Access Program.

Should you have any questions, feel free to write to us at or post a comment below.

Posted in General, IntelliJ Platform, Plugin Repository | Tagged , , | Leave a comment

Plugins Repository now integrates with the Plugin Verification tool

As our plugin eco-system grows, we want to give developers the same experience they have come to expect from our IDEs. Today we are happy to announce the integration of the Plugin Verifier tool for the Plugins Repository. This will allow you to check the binary compatibility between the IntelliJ IDEA‑based IDE builds and the IntelliJ Platform plugins as you upload them.

This tool is useful as it allows authors to check the plugins against a specified range of [since : until] builds for the platform, and not just against the current version of their editor. This process is needed as sometimes the IntelliJ API changes between releases. In turn, these changes might lead to binary incompatibilities between the plugin and the target platform, and so lead to NoClassDefFoundError, NoSuchMethodError, and similar exceptions at runtime.

With the recent update of the Plugins Repository, you can see the results of the plugin verification for each update of an IntelliJ Platform plugin which has been uploaded to the Plugins Repository.

The results of the verification are available in the Update Details View.
This is how it looks for one of the latest Scala plugin updates:

Scala plugin verification results

You can view the compatibility report and dive into the technical information about all the issues found.

In addition to this, you can schedule verification for a particular IDE build.

Please report all the bugs and feature requests to the Plugins Repository YouTrack Project.

Posted in IntelliJ Platform, Plugin Repository | Tagged , | 2 Comments

Legal News: Plugin License is Required for all Plugins

With the GDPR (General Data Protection Regulation) coming into action last week, in addition to some of the compliance-related changes which were introduced earlier, there has been a change to the way plugins and their updates are uploaded to the plugin repository.

Starting May 24, 2018, it is a requirement to specify a valid license URL for your plugins. Please provide a valid license URL for your plugins at your earliest convenience.

  • A License URL for new plugins should be provided on the upload form.
  • For existing plugins, it is not possible to upload a new update to the plugin unless the License URL is provided on the Edit Plugin page. If you are using an API to upload the plugin update and the license is not specified, an error will be returned until the License URL is provided in the plugins repository interface.


The owner or creator of the plugin decides what EULA (end-user license agreement) should apply to the plugin and its updates. Unfortunately, JetBrains can’t tell you what your plugin’s Developer EULA should say because it will largely depend on your choice of how to license the plugin, and how to use personal data, etc. However, we can give you some pointers, e.g. Open Source licenses and various independent EULA generators (not affiliated with JetBrains).

Should you have any questions, please ask them to us here in the comments, post them to @JBPlatform Twitter, or drop us an email at

Posted in IntelliJ Platform, Plugin Repository, TeamCity Platform | Tagged , | 1 Comment