From 12adb6f1e2531438d41524106d2eb61a070d6a68 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Wed, 10 Apr 2024 17:22:10 +0200 Subject: [PATCH] plugin_compatibility.md: Intellij -> IntelliJ --- topics/basics/getting_started/plugin_compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/basics/getting_started/plugin_compatibility.md b/topics/basics/getting_started/plugin_compatibility.md index 7aecd4ff4..5c2deb8a0 100644 --- a/topics/basics/getting_started/plugin_compatibility.md +++ b/topics/basics/getting_started/plugin_compatibility.md @@ -21,7 +21,7 @@ Declaring a dependency on a module also expresses a plugin's compatibility with [](plugin_dependencies.md) describes the syntax for declaring plugin dependencies and optional plugin dependencies. This document describes the IntelliJ Platform modules' functionality to aid in determining the dependencies of a plugin. -The way dependency declarations are handled by the Intellij Platform is determined by the contents of the [plugin.xml](plugin_configuration_file.md) file: +The way dependency declarations are handled by the IntelliJ Platform is determined by the contents of the [plugin.xml](plugin_configuration_file.md) file: * 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. This configuration of the dependency declaration is deprecated; do not use it for new plugin projects. * 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.