Nikolay Chashnikov 5db802c044 [rdct] create a special MigratePluginsFromCustomPlace option and use it to migrate plugins from the IDE to the frontend (RDCT-1393) ...

When a frontend process starts for the first time on a machine where the corresponding major version of the regular IDE has been already used, we need to migrate some plugins (e.g., keymaps) from the IDE to the frontend. Before it was done using the existing MigrateFromCustomPlace option. However, with such an approach, the whole config directory for the frontend process (which already has some files) is deleted and replaced by the IDE's config directory. And this causes problems, e.g., because it tries to back up and remove the 'process.lock' file. Since we need to migrate only plugins in this case, it's better to have a special config migration option for that. So MigratePluginsFromCustomPlace is introduced, and ConfigImportHelper is changed to run 'migratePlugins' only if this option is used.

This logic will be removed later when the frontend process starts to use the same directory for downloaded plugins as a regular IDE (see RDCT-1738).


(cherry picked from commit e1325d9c9b3866b692a0e20bcdb8cd8e15344ca0)

IJ-CR-147196

GitOrigin-RevId: 632de6d78c8e694dfde0bae87c4bab59d9eeddcd

2024-10-23 10:30:26 +00:00

..

coroutine

bazel - build lang-impl

2024-09-27 13:47:17 +00:00

dev

…

src/com/intellij

[rdct] create a special MigratePluginsFromCustomPlace option and use it to migrate plugins from the IDE to the frontend (RDCT-1393)

2024-10-23 10:30:26 +00:00

api-dump.txt

…

BUILD.bazel

…

intellij.platform.bootstrap.iml

IJ-CR-146078 extract intellij.platform.bootstrap

2024-10-05 22:01:55 +00:00