The IntelliJ Platform IDEs may recommend a plugin for installation in one of the following cases:
If a project contains files of types which are unsupported by the running IDE but are supported by a plugin available in the plugin repository.
If a project was created in different IDE installation which had the plugin installed, and includes shared settings (modules, facets, artifacts, or run configurations) configured using the plugin.
IntelliJ Platform IDEs only show plugin suggestions in the appropriate context, so they are meaningful to the user.
Features implemented by third-party plugins are subject to review and approval by JetBrains Marketplace, and must meet the approval criteria. We may establish additional criteria on a case-by-case basis and reserve the right to reject the feature implementation.
The Feature Extractor tool catalogs these types of features for a plugin. It works by statically analyzing the bytecode of a plugin to extract values passed to the IntelliJ Platform APIs that support extending features in the above list.
However, if values are dynamically evaluated in a plugin, the feature extractor may return incomplete results.
If you cannot find your plugin in the list of features, you can either make your code easier for the analysis or ask JetBrains to add manually any missed feature types.
File TypeA plugin can support specific File Types. When there is a file with a specific extension, pattern or name open in an IDE, a hint will be shown to users prompting them to install your plugin.
Both variants are supported by the feature extractor:
Extend FileTypeFactory and feed supported file extensions/exact file name matches in createFileTypes(FileTypeConsumer), values of FileTypeConsumer are analyzed.
Register com.intellij.fileType extension point (available in 2019.2+), all attributes are analyzed.
A suggestion to install plugins which support the _\*.d_ Extension Type:
Refer to Registering a File Type to provide this feature in a plugin.
Please note, that a file type won't get recommended if it conflicts with a bundled file type.
Run Configuration TypeWhen you want IDEs to show that your plugin supports Run Configuration Type, you need to implement ConfigurationType and implement the getId() method. The feature extractor analyzes the value of getId().
A suggestion to install plugins that support the Run D App Configuration Type:
Refer to Run Configurations to get more information about how to declare this feature in your plugin.
Facet TypeTo support a Facet Type feature, you should extend FacetType, and pass stringId to its constructor. The value of the stringId parameter will be analyzed by the feature extractor.
A notification to install plugins that support the jangaroo Facet Type:
Refer to Facet for additional information.
Module TypeIf you want IDEs to show a prompt that your plugin can support creating specific Module Types, you should extend ModuleType and pass the id parameter for your Module Type to its constructor. The feature extractor will evaluate the values of id.
See Module and Supporting Module Types for more information about supporting Module Types.
Artifact TypeTo support specific Artifact Types, extend ArtifactType, and pass an id parameter to its constructor. The value of the id parameter is analyzed by the feature extractor.
An example suggestion to enable a plugin which supports a dm.bundle Artifact Type:
Dependency SupportWe do not accept any 3rd party dependency support features temporarily. We have a new kind of dependencySupport executable starting from 2023.2 which is still in testing.
To support a specific dependency you should declare a tag like
<dependencySupport kind="java" coordinate="org.junit:org.junit" displayName="Junit"/>
in the plugin.xml file.
Last modified: 23 January 2024
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4