diff --git a/topics/basics/getting_started/publishing_plugin.md b/topics/basics/getting_started/publishing_plugin.md index 0bc92d768..7dcace8a6 100644 --- a/topics/basics/getting_started/publishing_plugin.md +++ b/topics/basics/getting_started/publishing_plugin.md @@ -95,25 +95,10 @@ This section describes two options to supply the _Personal Access Token_ via Gra Start by defining an environment variable such as: - - - - ```bash -export ORG_GRADLE_PROJECT_intellijPlatform.publishing.token='YOUR_TOKEN' +export ORG_GRADLE_PROJECT_intellijPlatformPublishingToken='YOUR_TOKEN' ``` - - - - -```bash -export ORG_GRADLE_PROJECT_intellijPublishToken='YOUR_TOKEN' -``` - - - - > On macOS systems, environment variables set in .bash_profile are only visible to processes run from bash. > Environment variables visible to all processes need to be defined in [Environment.plist](https://developer.apple.com/library/archive/qa/qa1067/_index.html). > @@ -124,48 +109,27 @@ Now provide the environment variable in the run configuration for running the `p To do so, create a Gradle run configuration (if not already done), select the Gradle project, specify the `publishPlugin` task, and then add the environment variable. -##### IntelliJ Platform Gradle Plugin (2.x) + - - + ```kotlin -publishPlugin { - token.set(System.getenv("ORG_GRADLE_PROJECT_intellijPlatform.publishing.token")) +intellijPlatform { + publishing { + token = providers.gradleProperty("intellijPlatformPublishingToken") + } } ``` - -```groovy -publishPlugin { - token = System.getenv("ORG_GRADLE_PROJECT_intellijPlatform.publishing.token") -} -``` - - - - -##### Gradle IntelliJ Plugin (1.x) - -{collapsible="true" default-state="collapsed"} - - - + ```kotlin -publishPlugin { - token.set(System.getenv("ORG_GRADLE_PROJECT_intellijPublishToken")) -} -``` - - - - -```groovy -publishPlugin { - token = System.getenv("ORG_GRADLE_PROJECT_intellijPublishToken") +tasks { + publishPlugin { + token = providers.gradleProperty("intellijPlatformPublishingToken") + } } ``` @@ -179,25 +143,10 @@ Note that it's still required to put some default values (can be empty) in the G Like using environment variables, the token can also be passed as a parameter to the Gradle task. For example, provide the parameter on the command line or by putting it in the arguments of the Gradle run configuration. - - - - ```bash --Dorg.gradle.project.intellijPlatform.publishing.token=YOUR_TOKEN +-PintellijPlatformPublishingToken=YOUR_TOKEN ``` - - - - -```bash --Dorg.gradle.project.intellijPublishToken=YOUR_TOKEN -``` - - - - Note that in this case also, it's still required to put some default values (can be empty) in the Gradle properties ### Deploying a Plugin with Gradle @@ -226,15 +175,21 @@ If successfully deployed, any users who currently have this plugin installed on ### Specifying a Release Channel -It's possible to deploy plugins to a chosen release channel by configuring the `publishPlugin.channels` property -(Reference: [2.x](tools_intellij_platform_gradle_plugin_tasks.md#publishPlugin-channels), [1.x](tools_gradle_intellij_plugin.md#tasks-publishplugin-channels)). + + + + +It's possible to deploy plugins to a chosen release channel by configuring the [`intellijPlatform.publishing.channels`](tools_intellij_platform_gradle_plugin_extension.md#intellijPlatform-publishing-channels) extension property. + ```kotlin -publishPlugin { - channels.set(listOf("beta")) +intellijPlatform { + publishing { + channels = listOf("beta") + } } ``` @@ -242,14 +197,49 @@ publishPlugin { ```groovy -publishPlugin { - channels = ['beta'] +intellijPlatform { + publishing { + channels = ['beta'] + } } ``` + + + +It's possible to deploy plugins to a chosen release channel by configuring the [`publishPlugin.channels`](tools_gradle_intellij_plugin.md#tasks-publishplugin-channels) task property. + + + + +```kotlin +tasks { + publishPlugin { + channels = listOf("beta") + } +} +``` + + + + +```groovy +tasks { + publishPlugin { + channels = ['beta'] + } +} +``` + + + + + + + When empty, this uses the default plugin repository, available to all [JetBrains Marketplace](https://plugins.jetbrains.com/) users. However, it's possible to publish it to an arbitrarily named channel. These non-default release channels are treated as separate repositories.