From 31e5236c543b4c4f7040a88dcc6a46c16e1855e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Tue, 1 Oct 2024 12:11:46 +0200 Subject: [PATCH] custom_plugin_repository.md: cleanup --- .../resources/custom_plugin_repository.md | 51 ++++++++++++------- 1 file changed, 34 insertions(+), 17 deletions(-) diff --git a/topics/appendix/resources/custom_plugin_repository.md b/topics/appendix/resources/custom_plugin_repository.md index 8f56c31c8..17225977a 100644 --- a/topics/appendix/resources/custom_plugin_repository.md +++ b/topics/appendix/resources/custom_plugin_repository.md @@ -4,30 +4,41 @@ Creating custom plugin repositories other than JetBrains Marketplace. -> [IDE Provisioner](https://www.jetbrains.com/ide-services/ide-provisioner/) comes with a local built-in repository of IntelliJ Platform plugins that allows you to choose specific plugins to be approved within your organization. It also lets you upload and distribute your own plugins inside your company, as well as any publicly available plugin from the internet. + -If you intend to use a plugin repository _other than_ the [JetBrains Marketplace](https://plugins.jetbrains.com), you will need to: +**Product Help**: [Repository Settings](https://www.jetbrains.com/help/idea/managing-plugins.html#repos) - + -1. Create and maintain an updatePlugins.xml* file on the HTTPS web server you are using for your custom repository. - This file describes all the plugins available in your custom repository and each plugin's download URL. -2. Upload your plugin JAR/ZIP file to an HTTPS web server. - This can be the same web server you are using for the custom repository or a different HTTPS web server. +> [IDE Provisioner](https://www.jetbrains.com/ide-services/ide-provisioner/) comes with a local built-in repository of IntelliJ Platform plugins +> that allows choosing specific plugins to be approved within an organization. +> It also allows uploading and distributing private plugins inside an organization, as well as any publicly available plugin from the internet. +> +{title="JetBrains IDE Services: IDE Provisioner"} + +To use a plugin repository _other than_ the [JetBrains Marketplace](https://plugins.jetbrains.com), perform the following steps: + + + +1. Create and maintain an updatePlugins.xml1 file on the HTTPS web server used for the custom repository. + This file describes all the plugins available in the custom repository and each plugin's download URL. +2. Upload the plugin distribution JAR/ZIP file to an HTTPS web server. + This can be the same web server used for the custom repository or a different HTTPS web server. 3. Add the URL for the custom repository to the JetBrains IDE [Repository Settings](https://www.jetbrains.com/help/idea/managing-plugins.html#repos). -\* The updatePlugin.xml file name is not fixed and can be different. +1 The updatePlugin.xml filename is not fixed and can be different. > Gradle plugin [IntelliJ plugin uploader](https://github.com/brian-mcnamara/plugin_uploader) can be used to automate deployment. > +{title="Automating Deployment"} To avoid collisions between private plugins and those hosted on JetBrains Marketplace, an organization can [reserve plugin IDs](https://plugins.jetbrains.com/docs/marketplace/reserved-plugin-ids.html). To provide custom authentication, implement [`PluginRepositoryAuthProvider`](%gh-ic%/platform/platform-impl/src/com/intellij/ide/plugins/auth/PluginRepositoryAuthProvider.java) registered in `com.intellij.pluginRepositoryAuthProvider` extension point. -## Describing Your Plugins in updatePlugins.xml File +## Describing Plugins in `updatePlugins.xml` File Every custom plugin repository must have at least one updatePlugins.xml file to describe every hosted plugin's latest available version. The description in updatePlugins.xml is used by JetBrains IDEs to locate plugins by attributes such as identifier, IDE version, and plugin version. @@ -39,7 +50,7 @@ More than one updatePlugins.xml file may be required if the custom For example, updatePlugins-182.xml, updatePlugins-183.xml for IntelliJ IDEA 2018.2 and 2018.3, respectively. Each updatePlugins-*.xml file will have a unique URL that is added to the JetBrains IDE [Repository Settings](https://www.jetbrains.com/help/idea/managing-plugins.html#repos). -### Format of updatePlugins.xml File +### Format of `updatePlugins.xml` File The format of an updatePlugins.xml file is simply a list of sequential elements that describe each plugin: @@ -61,9 +72,9 @@ available at this repository. in the plugin.xml file. --> + id="fully.qualified.id.of.this.plugin" + url="https://mycompany.example.com/my_repo/my_plugin.jar" + version="major.minor.update"> @@ -87,7 +98,13 @@ available at this repository. * Multiple plugins with the same `id` but different `idea-version` attributes must be split into separate updatePlugins-*.xml files. The requesting IDE's version is passed as `build` parameter and can be used for server-side filtering. -### Optional updatePlugin.xml Elements +### Optional `updatePlugin.xml` Elements + + + +**Reference**: [](plugin_configuration_file.md) + + During plugin installation, the IDE reads the plugin JAR/ZIP file and thereafter displays more information about the plugin. In some cases, additional information included in updatePlugins.xml might help a user select a plugin when [browsing the custom plugin repository](https://www.jetbrains.com/help/idea/managing-plugins.html#repos) before installation.