mirror of
https://github.com/JetBrains/intellij-sdk-code-samples.git
synced 2025-07-29 01:37:51 +08:00
84 lines
4.0 KiB
Markdown
84 lines
4.0 KiB
Markdown
---
|
|
title: Dynamic Plugins
|
|
---
|
|
<!-- Copyright 2000-2020 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
|
|
|
|
Starting with 2020.1 release, the ability to install, update and uninstall plugins without restarting the IDE is available in the IntelliJ Platform.
|
|
During plugin development, [Auto-Reload](/basics/ide_development_instance.md#enabling-auto-reload) also allows code changes to take effect immediately in the sandbox IDE instance.
|
|
|
|
> **NOTE** If a plugin _requires_ restart (e.g., due to using native libraries) specify `require-restart="true"` for `<idea-plugin>` root tag in `plugin.xml`.
|
|
|
|
## Restrictions
|
|
|
|
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 Plugins 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.
|
|
|
|
### No Use of Components
|
|
|
|
No Components must be used; existing ones [must be migrated](plugin_components.md) to services, extensions or listeners.
|
|
|
|
### Action Group Requires ID
|
|
|
|
All `<group>`s must declare a unique `id`.
|
|
|
|
### Use Only Dynamic Extensions
|
|
|
|
All extensions, whether defined in the platform itself or coming from other plugins, must be marked as dynamic (see next paragraph).
|
|
|
|
Some deprecated extension points (e.g., `com.intellij.configurationProducer`) are intentionally non-dynamic, and their usage should be migrated to the corresponding replacement.
|
|
|
|
### Mark Extension Points as Dynamic
|
|
|
|
All extension points provided by the plugin must adhere to specific usage rules and then [be declared](plugin_extension_points.md#dynamic-extension-points) ready for dynamic use explicitly.
|
|
|
|
### Configurables Depending on Extension Points
|
|
|
|
Any `Configurable` which depends on dynamic extension points must implement `Configurable.WithEpDependencies`.
|
|
|
|
### No Use of Service Overrides
|
|
|
|
Application, project and module services declared with `overrides="true"` are not allowed.
|
|
|
|
## Code
|
|
|
|
> **NOTE** Loading and unloading plugins happens in EDT and under write action.
|
|
|
|
### CachedValue
|
|
|
|
Loading/Unloading a plugin clears all cached values created using `CachedValuesManager`.
|
|
|
|
### Do not Store PSI
|
|
|
|
Do not store references to PSI elements in objects which can survive plugin loading or unloading, use `SmartPsiElementPointer` instead.
|
|
|
|
### Do not Use FileType/Language as Map Key
|
|
|
|
Replace with `String` from `Language.getID()`/`FileType.getName()`.
|
|
|
|
### Plugin Load/Unload Events
|
|
|
|
Register [`com.intellij.ide.plugins.DynamicPluginListener`](upsource:///platform/platform-impl/src/com/intellij/ide/plugins/DynamicPlugins.kt) [application listener](plugin_listeners.md) to receive updates on plugin load/unload events.
|
|
|
|
This can be used to e.g. cancel long-running activities or disallow unload due to ongoing processes.
|
|
|
|
## Troubleshooting
|
|
|
|
When a plugin is being uninstalled or updated, the IDE waits synchronously for plugin unload and asks for restart if the unload failed.
|
|
|
|
### Logging
|
|
|
|
All events are tracked under `com.intellij.ide.plugins.DynamicPlugins` category in IDE log file.
|
|
|
|
### Diagnosing Leaks
|
|
|
|
To find leaks preventing clean unload, perform the following steps:
|
|
|
|
- Set registry key `ide.plugins.snapshot.on.unload.fail` to `true`
|
|
- Verify that IDE runs with VM parameter `-XX:+UnlockDiagnosticVMOptions`
|
|
- Open the `.hprof` snapshot generated on plugin unload, look for the plugin ID string
|
|
- Find the `PluginClassLoader` referencing the plugin ID string
|
|
- Look at references to the `PluginClassLoader` instance. Every one of them is a memory leak (or part of a memory leak) that needs to be resolved.
|