From 00d940a3709906a257ae1b9d7be75b51d83c0f7d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Thu, 14 May 2020 15:31:49 +0200 Subject: [PATCH] move obsolete plugin_repository into /appendix and stop linking to it --- _SUMMARY.md | 2 +- .../index.md => appendix/plugin_repository_obsolete.md | 3 ++- basics/plugin_structure/dynamic_plugins.md | 2 +- intro/about.md | 2 +- reference_guide/api_changes_list.md | 4 ++-- tutorials/build_system.md | 2 +- 6 files changed, 8 insertions(+), 7 deletions(-) rename plugin_repository/index.md => appendix/plugin_repository_obsolete.md (96%) diff --git a/_SUMMARY.md b/_SUMMARY.md index d0538e91e..9e5eb02b9 100644 --- a/_SUMMARY.md +++ b/_SUMMARY.md @@ -255,7 +255,7 @@ * Licensing ## Part X - Plugin Repository \[moved] -* [Overview](plugin_repository/index.md) +* [Overview](appendix/plugin_repository_obsolete.md) ## Appendix I - Resources diff --git a/plugin_repository/index.md b/appendix/plugin_repository_obsolete.md similarity index 96% rename from plugin_repository/index.md rename to appendix/plugin_repository_obsolete.md index 8997ff2a4..e04a91831 100644 --- a/plugin_repository/index.md +++ b/appendix/plugin_repository_obsolete.md @@ -1,7 +1,8 @@ --- -title: Plugin Repository +title: Plugin Repository [moved] redirect_from: + - /plugin_repository/index.html - /plugin_repository/api/api_reference.html - /plugin_repository/api/plugin_upload.html - /plugin_repository/api/plugins_list.html diff --git a/basics/plugin_structure/dynamic_plugins.md b/basics/plugin_structure/dynamic_plugins.md index 8552dcc22..9ac1790e3 100644 --- a/basics/plugin_structure/dynamic_plugins.md +++ b/basics/plugin_structure/dynamic_plugins.md @@ -10,7 +10,7 @@ Starting with 2020.1 release, the ability to install, update and uninstall plugi For a plugin to support this, all restrictions listed below must be met. To verify a plugin locally, run _Plugin DevKit | Plugin descriptor | Plugin.xml dynamic plugin verification_ inspection on all plugin descriptor files (required `plugin.xml` as well as any additional files). -For plugins hosted on the [JetBrains plugin repository](/plugin_repository/index.md) the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/) +For plugins hosted on the [JetBrains plugin repository](https://plugins.jetbrains.com) the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/) will run these checks automatically. See [Plugin Verifier](/reference_guide/api_changes_list.md#plugin-verifier) for more information on how to run it locally. During development, [Enabling Auto-Reload](/basics/ide_development_instance.md#enabling-auto-reload) will allow code changes to take effect immediately in the sandbox IDE instance. diff --git a/intro/about.md b/intro/about.md index 8e727d317..27772ab97 100644 --- a/intro/about.md +++ b/intro/about.md @@ -45,7 +45,7 @@ A lot of the functionality in the _IntelliJ Platform_ is language and product ag Documents how to use the _IntelliJ Platform_ to create a new, custom IDE, rather than plugins to an existing product, e.g. like WebStorm, or Android Studio. -#### [Part X - Plugin Repository](/plugin_repository/index.md) +#### [Part X - Plugin Repository](/appendix/plugin_repository_obsolete.md) This part has been moved to [JetBrains Marketplace documentation](https://plugins.jetbrains.com/docs/marketplace/about-marketplace.html). diff --git a/reference_guide/api_changes_list.md b/reference_guide/api_changes_list.md index 8e246eba3..71194162f 100644 --- a/reference_guide/api_changes_list.md +++ b/reference_guide/api_changes_list.md @@ -65,14 +65,14 @@ NOTE: Entries not starting with code quotes (`name`) can be added to document no IntelliJ API may be occasionally changed between releases, leading to incompatibilities of existing plugins with newer IDE builds. ## Verifying Compatibility ### Plugin Verifier -Compatibility with newer IDEs can easily be verified for plugins hosted on the [JetBrains plugin repository](/plugin_repository/index.md) using the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/). +Compatibility with newer IDEs can easily be verified for plugins hosted on the [JetBrains plugin repository](https://plugins.jetbrains.com) using the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/). For local verification or non-public plugins, [intellij-plugin-verifier](https://github.com/JetBrains/intellij-plugin-verifier) can be used standalone as well. Integration in [Gradle build](/tutorials/build_system.md) is currently possible via some additional scripts, please see [this issue](https://github.com/JetBrains/gradle-intellij-plugin/issues/385) for details. diff --git a/tutorials/build_system.md b/tutorials/build_system.md index 4237a3080..a62c364fe 100644 --- a/tutorials/build_system.md +++ b/tutorials/build_system.md @@ -8,7 +8,7 @@ The plugin takes care of the dependencies of your plugin project - both the base > **NOTE** If a new plugin will be Scala-based, a dedicated SBT plugin [sbt-idea-plugin](https://github.com/JetBrains/sbt-idea-plugin) is available. -The gradle-intellij-plugin provides tasks to run the IDE with your plugin and to publish your plugin to the [JetBrains plugins repository](/plugin_repository/index.md). +The gradle-intellij-plugin provides tasks to run the IDE with your plugin and to publish your plugin to the [JetBrains plugins repository](https://plugins.jetbrains.com). To make sure that your plugin is not affected by [API changes](/reference_guide/api_changes_list.md) which may happen between major releases of the platform, you can easily build your plugin against many versions of the base IDE. > **WARNING** When adding additional repositories to your Gradle build script, make sure to always use HTTPS protocol.