For example, the module supports the Python language-specific functionality. More specialized functionality is also delivered via modules and plugins in IntelliJ Platform-based products. VCS Revision Numbers, File Status, Change Lists, File History, Annotationsĭebug Session, Stack Frames, Break Points, Source Positions, Memory Views, Tracked InstancesĪs of this writing, if a plugin: A) is dependent only on one or more of the modules in the table above, and B) declares those module dependencies in plugin.xml, then any product developed by JetBrains based on the IntelliJ Platform will load it. Messaging, Themes, UI Components, Files, Documents, Actions, Components, Services, Extensions, Editorsįile Type, Lexer, Parser, Highlighting, References, Code Completion, Find, Rename, Formatter, Code Navigation The following table lists modules that are currently available in all products.Īll plugins should declare a dependency on to indicate dependence on shared functionality. These modules provide a set of shared functionalities. ![]() Modules Available in All ProductsĪ core set of modules is available in all products based on the IntelliJ Platform. Starting in 2020.2, a plugin can declare incompatibility with an arbitrary module by specifying containing module ID in its plugin.xml. This section identifies and discusses modules of both types. Some modules are available in all products, and some modules are available only in some, or even just one product. If a plugin declares at least one module dependency in its plugin.xml file, the plugin is loaded if an IntelliJ Platform-based product contains all the modules and plugins on which the plugin has declared a dependency.Ī module represents a built-in plugin that is a non-removable part of a product. This configuration of the dependency declaration is deprecated do not use it for new plugin projects. If a plugin does not declare any dependencies in its plugin.xml file, or if it declares dependencies only on other plugins but not modules, it's assumed to be a legacy plugin and is loaded only in IntelliJ IDEA. The way dependency declarations are handled by the Intellij Platform is determined by the contents of the plugin.xml file: This document describes the IntelliJ Platform modules' functionality to aid in determining the dependencies of a plugin. Plugin Dependencies describes the syntax for declaring plugin dependencies and optional plugin dependencies. Declaring a dependency on a module also expresses a plugin's compatibility with a product in that the IntelliJ Platform determines whether a product contains the correct modules to support a plugin before loading it. A working definition of a dependency is that a plugin project cannot be run without the module present in an IntelliJ Platform-based product. Declaring Plugin Dependenciesįor the purposes of dependencies, a module can be thought of as a built-in plugin that ships as a non-removable part of a product. Qualifying Open Source projects can apply for free licenses of JetBrains products. Otherwise, it may not be possible to load or run the plugin in a product because the components on which it depends aren't available. ![]() ![]() When authoring a plugin for the IntelliJ Platform, it is important to understand and declare dependencies on these components. Underlying those shared features are shared components. Some of these products share features built on top of the platform, such as Java support in IntelliJ IDEA and Android Studio. ![]() Plugin Compatibility with IntelliJ Platform ProductsĪll products based on the IntelliJ Platform are built on the same underlying API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |