plugin_alternatives.md: Flora is in an experimental state

This commit is contained in:
Karol Lewandowski 2024-03-21 08:51:49 +01:00
parent 1ace97a239
commit d3a72f2776

View File

@ -1,6 +1,6 @@
# Alternatives to Implementing a Plugin
<!-- Copyright 2000-2024 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. -->
<!-- Copyright 2000-2023 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. -->
# Alternatives to Implementing a Plugin
<link-summary>Alternative strategies and tools to avoid building a "full" plugin.</link-summary>
@ -43,6 +43,8 @@ Every extension is represented by a single file and stored directly in a project
Extensions can be easily shared with other team members by adding the <path>.plugins</path> directory to VCS.
Also, adding the Flora plugin in the <ui-path>Settings | Build, Execution, Deployment | Required Plugins</ui-path> and sharing this configuration as part of a project makes it effortless to deliver additional IDE functionalities to your team without any manual setup.
> Please note that the Flora plugin is in an experimental state.
## LivePlugin
The [LivePlugin](https://plugins.jetbrains.com/plugin/7282-liveplugin) allows for extending IntelliJ-based IDEs functionalities at the runtime, without the need of restarting IDE.