hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-30 02:07:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into patch-1

Browse Source
This commit is contained in:
Inego 2018-04-22 18:36:58 +07:00
commit 886a7afcd7
4 changed files with 22 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
basics/getting_started/using_dev_kit.md
View File

@ -7,10 +7,10 @@ own build system. It provides its own SDK type and a set of actions for building
In this section: In this section:
* [Setting Up a Development Environment](getting_started/setting_up_environment.md) * [Setting Up a Development Environment](setting_up_environment.md)
* [Check Out And Build Community Edition](basics/checkout_and_build_community.md) * [Check Out And Build Community Edition](../checkout_and_build_community.md)
* [Creating a Plugin Project](getting_started/creating_plugin_project.md) * [Creating a Plugin Project](creating_plugin_project.md)
* [Creating an Action](getting_started/creating_an_action.md) * [Creating an Action](creating_an_action.md)
* [Running and Debugging a Plugin](getting_started/running_and_debugging_a_plugin.md) * [Running and Debugging a Plugin](running_and_debugging_a_plugin.md)
* [Deploying a Plugin](getting_started/deploying_plugin.md) * [Deploying a Plugin](deploying_plugin.md)
* [Publishing a plugin to plugin repository](getting_started/publishing_plugin.md) * [Publishing a plugin to plugin repository](publishing_plugin.md)

8
plugin_repository/api/plugin_upload.md
View File

@ -20,13 +20,13 @@ Parameters:
Provide file as file contents. Curl command template: Provide file as file contents. Curl command template:
``` ```
curl -k -i -F userName=<userName> -F password=<password> -F pluginId=<pluginId> -F file=@<path to plugin .jar/.zip file> -F channel=<channel> https://plugins.jetbrains.com/plugin/uploadPlugin curl -i -F userName=<userName> -F password=<password> -F pluginId=<pluginId> -F file=@<path to plugin .jar/.zip file> -F channel=<channel> https://plugins.jetbrains.com/plugin/uploadPlugin
``` ```
Curl command example: Curl command example:
``` ```
curl -k -i -F userName=pluginrobot -F password=123456 -F pluginId=5047 -F file=@Go-0.11.1197.zip -F channel=nightly https://plugins.jetbrains.com/plugin/uploadPlugin curl -i -F userName=pluginrobot -F password=123456 -F pluginId=5047 -F file=@Go-0.11.1197.zip -F channel=nightly https://plugins.jetbrains.com/plugin/uploadPlugin
``` ```
**Using pluginXmlId** **Using pluginXmlId**
@ -34,11 +34,11 @@ curl -k -i -F userName=pluginrobot -F password=123456 -F pluginId=5047 -F file=@
Provide file as file contents. Curl command template: Provide file as file contents. Curl command template:
``` ```
curl -k -i -F userName=<userName> -F password=<password> -F xmlId=<pluginXmlId> -F file=@<path to plugin .jar/.zip file> -F channel=<channel> https://plugins.jetbrains.com/plugin/uploadPlugin curl -i -F userName=<userName> -F password=<password> -F xmlId=<pluginXmlId> -F file=@<path to plugin .jar/.zip file> -F channel=<channel> https://plugins.jetbrains.com/plugin/uploadPlugin
``` ```
Curl command example: Curl command example:
``` ```
curl -k -i -F userName=pluginrobot -F password=123456 -F xmlId=ro.redeul.google.go -F file=@Go-0.11.1197.zip -F channel=nightly https://plugins.jetbrains.com/plugin/uploadPlugin curl -i -F userName=pluginrobot -F password=123456 -F xmlId=ro.redeul.google.go -F file=@Go-0.11.1197.zip -F channel=nightly https://plugins.jetbrains.com/plugin/uploadPlugin
``` ```

10
reference_guide/api_changes/api_changes_list_2018.md
View File

@ -15,6 +15,16 @@ See the note on how to document new problems on the main page reference_guide/ap
} }
</style> </style>
## Changes in IntelliJ Platform 2018.2
| Change | How to deal with it |
|---------|---------------------|
| `com.intellij.util.Query.forEach` method parameter type changed from `Processor<Result>` to `Processor<? super Result>` | Update `Query` implementations accordingly |
| `com.intellij.util.Query.forEachAsync` method parameter type changed from `Processor<Result>` to `Processor<? super Result>` | Update `Query` implementations accordingly |
| `com.intellij.util.QueryExecutor.execute` method parameter type changed from `Processor<Result>` to `Processor<? super Result>` | Update `QueryExecutor` implementations accordingly |
| `com.intellij.openapi.application.QueryExecutorBase.processQuery` method parameter type changed from `Processor<Result>` to `Processor<? super Result>` | Update `QueryExecutorBase` inheritors accordingly |
| `com.intellij.util.InstanceofQuery` type parameter `T` added | Set this parameter at call sites to base query type |
## Changes in IntelliJ Platform 2018.1 ## Changes in IntelliJ Platform 2018.1
| Change | How to deal with it | | Change | How to deal with it |

2
user_interface_components/tool_windows.md
View File

@ -16,7 +16,7 @@ There are two main scenarios for the use of tool windows in a plugin.
In the first scenario (used by the Ant and Commander plugins, for example), a tool window button is always visible, and the user can activate it and interact with the plugin functionality at any time. In the first scenario (used by the Ant and Commander plugins, for example), a tool window button is always visible, and the user can activate it and interact with the plugin functionality at any time.
In the second scenario (used by the `Analyze Dependencies` action, for example), the tool window is created to show the results of a specific operation, and can be closed by the user after the operation is completed. In the second scenario (used by the `Analyze Dependencies` action, for example), the tool window is created to show the results of a specific operation, and can be closed by the user after the operation is completed.
In the first scenario, the tool window is registered in *plugin.xml* using the `<tool window>` extension point. In the first scenario, the tool window is registered in *plugin.xml* using the `<toolWindow>` extension point.
The extension point attributes specify all the data which is necessary to display the tool window button: The extension point attributes specify all the data which is necessary to display the tool window button:
* The `id` of the tool window (corresponds to the text displayed on the tool window button) * The `id` of the tool window (corresponds to the text displayed on the tool window button)