tools_intellij_platform_gradle_plugin_dependencies_extension.md: note about repos

This commit is contained in:
Yann Cébron 2024-07-30 13:51:42 +02:00
parent bafd061673
commit 3606da492b
2 changed files with 17 additions and 9 deletions

View File

@ -164,6 +164,8 @@ To apply required repositories, use [](tools_intellij_platform_gradle_plugin_rep
## Plugins ## Plugins
Make sure that required [](tools_intellij_platform_gradle_plugin_repositories_extension.md#plugin-repositories) are defined to access non-bundled plugins.
> Use the correct function depending on whether the > Use the correct function depending on whether the
> targeted plugin is _bundled_ with the Target Platform or not. > targeted plugin is _bundled_ with the Target Platform or not.
> >

View File

@ -101,10 +101,19 @@ If the plugin is not bundled with the target IDE, run the (sandbox) [IDE Develop
## 2. Project Setup ## 2. Project Setup
Depending on the chosen development workflow (Gradle or DevKit), one of the two following steps is necessary. Depending on the chosen development workflow (Gradle or DevKit), one of the following steps is necessary.
<tabs> #### IntelliJ Platform Gradle Plugin (2.x)
<tab title="Gradle">
**Bundled Plugin**: Use `bundledPlugin()`
**Non-Bundled Plugin**: Use `plugin()`
See [](tools_intellij_platform_gradle_plugin_dependencies_extension.md#plugins) for full reference.
#### Gradle IntelliJ Plugin (1.x)
{collapsible="true" default-state="collapsed"}
> Please see the [`intellij.plugins`](tools_gradle_intellij_plugin.md#intellij-extension-plugins) property for acceptable values. > Please see the [`intellij.plugins`](tools_gradle_intellij_plugin.md#intellij-extension-plugins) property for acceptable values.
> >
@ -136,9 +145,10 @@ intellij {
> Transitive dependencies required for tests must currently be [specified explicitly](https://github.com/JetBrains/gradle-intellij-plugin/issues/38). > Transitive dependencies required for tests must currently be [specified explicitly](https://github.com/JetBrains/gradle-intellij-plugin/issues/38).
> >
{style="note"} {style="note"}
</tab>
<tab title="DevKit"> ### Plugin DevKit
{collapsible="true" default-state="collapsed"}
> Existing DevKit-based projects can be [converted to use Gradle setup](migrating_plugin_devkit_to_gradle.md) where dependency management is fully automated. > Existing DevKit-based projects can be [converted to use Gradle setup](migrating_plugin_devkit_to_gradle.md) where dependency management is fully automated.
> >
@ -163,10 +173,6 @@ Add the JARs of the plugin on which the project depends to the <control>Classpat
</procedure> </procedure>
</tab>
</tabs>
## 3. Dependency Declaration in plugin.xml ## 3. Dependency Declaration in plugin.xml
Regardless of whether a plugin project uses [](plugin_compatibility.md#modules-available-in-all-products), or [](plugin_compatibility.md#modules-specific-to-functionality), the correct module must be listed as a dependency in <path>plugin.xml</path>. Regardless of whether a plugin project uses [](plugin_compatibility.md#modules-available-in-all-products), or [](plugin_compatibility.md#modules-specific-to-functionality), the correct module must be listed as a dependency in <path>plugin.xml</path>.