Notable Changes in IntelliJ Platform and Plugins API 2019.*

Now reflects its "heavy test" characteristics (see Light and Heavy Tests).

Optional plugin.xml configuration files can now specify <depends>. Issue

(Un)Installing or enabling/disabling Theme or Keymap plugins doesn't require an IDE restart anymore.

Use com.intellij.ide.util.RunOnceUtil to run a task exactly once for application or per project.

Contribute symbol names (classes, methods, ...) via com.intellij.completion.plainTextSymbol extension point (PlainTextSymbolCompletionContributor).

Use com.intellij.util.text.JBDateFormat#getFormatter() to use configured format from Settings | Appearance & Behavior | System Settings | Date Formats.

Several plugins (Heroku integration, RubyMotion support, Java Applets Support) for no longer actively maintained technology have been moved to a separate repository. If your plugin depends on them, users will need to install them from the JetBrains Marketplace.

Consistent with other quickfixes, the menu now shows names of fixes, not names of problems themselves. Issue

Use com.intellij.openapi.editor.richcopy.HtmlSyntaxInfoUtil to create Lexer-based highlighted code samples, e.g., for usage in documentation.

Toggles showing additional details in UI (e.g. modification timestamp in Project View) see UISettings.getShowInplaceComments().

Allows a variety of presentations (incl. custom painting), mouse event handling, and exposing settings in Settings | Editor | Inlay Hints. See com.intellij.codeInsight.hints.InlayHintsProvider.

A non-blocking variant for com.intellij.openapi.vfs.newvfs.BulkFileListener.

Provides background color in all Trees, Lists and ComboBoxes.

Use new dedicated com.intellij.backgroundPostStartupActivity extension point (see Javadoc for StartupActivity#BACKGROUND_POST_STARTUP_ACTIVITY).

Use new dedicated com.intellij.highlightingPassFactory extension point.

When registering a file type via file extension, pattern, or exact filename matching, use com.intellij.fileType extension point instead (see Sample).

Indicates that the annotated API class, interface, or method must not get extended, implemented, or overridden by external plugins but can only be obtained or instantiated for classes and interfaces, or called for methods.

Indicates that the annotated method is part of SPI (Service Provider Interface), which is intended to be only implemented or overridden but never called by external plugins.

Defaults to thread-safe to prevent problems with clients using unsynchronized collections.

Returns dedicated message when invalid SDK path was chosen (e.g., JRE instead of JDK).

If your plugin depends on Java, it must be specified now; see Java for details.

Several plugins (J2ME, JsTestDriver, Struts 1.x) for no longer actively maintained technology have been moved to a separate repository. If your plugin depends on them, users will need to install them from the JetBrains Marketplace.

Use dedicated ProjectDescriptor or rollback project setup changes in tearDown() (see Light and Heavy Tests).

External annotations for the IntelliJ Platform are generated and attached to plugin projects automatically (replacing @since Javadoc).

External annotations for the IntelliJ Platform are generated and attached to plugin projects automatically. This allows highlighting of API, which has been removed in newer platform versions.

Indicates that the annotated element must not be considered as a public API. Do not use outside of the IntelliJ Platform, see Internal API Migration.

Assert references are created for the given underlying PsiElement. Issue

Enabled in tests and EAP/internal mode, see CachedValueStabilityChecker Javadoc.