Plugin Deprecations in IntelliJ IDEA v2019.2
Over the years, IntelliJ IDEA has accumulated support for a large array of technologies, and many of the technologies are no longer being actively maintained. We know that there are still people using these technologies, and up until now, we’ve been maintaining the plugins for them as part of the main IntelliJ IDEA source repository. However, our project has been growing, and carrying around this excess baggage is getting more and more difficult both for our users (as the plugins affect the size of the installation and potentially the performance of the IDE) and for our development team. At the same time, we’ve established procedures for maintaining a stable third-party plugin API, so we’re confident that moving the plugins out of the main repository will not affect their stability as the IDE evolves.
Starting with IntelliJ IDEA v2019.2, we’re going to move a number of plugins to a separate repository. These plugins will no longer be bundled with IntelliJ IDEA, and we will not be updating these plugins together with IntelliJ IDEA releases. However, you will still be able to download the plugins from the plugin repository, and we’ll try to fix any critical issues in the plugins if any are reported. The new repository is open-source, so you’re able to submit pull requests with fixes and improvements, and if you do, we will release updates of the plugins with your changes included.
The specific plugins affected by this in v2019.2 are:
- Struts 1.x and Tiles
We plan to continue with deprecation in future releases. Plugins considered for deprecation in v2019.3 include:
- Google App Engine (superseded by Google’s Cloud Code plugin)
- Emma code coverage
Your IntelliJ IDEA team