this fixes tests
in RunConfigurationSchemeManagerTest: `project loading - initially selected run config stored in run_xml file` and `set any run config as selected if no info`
GitOrigin-RevId: 7d4225a9ac127955e6b370b042ecbd936c06b0d4
yes, it is intended
(cherry picked from commit 0b4c9a2197c343382142ed88aec54eb87192d0ad)
IJ-CR-138667
GitOrigin-RevId: 4768bcef63b12840736c483b58b728db12b543d9
not necessary anymore (see the commit, when it was removed)
this should fix the failed test `FileComparisonFailedError: 'intellij.platform.execution.impl' API dump does not match the actual API`
(cherry picked from commit 1e38ad80468fcab9541c5989f83f7e2e4c4b0c72)
IJ-CR-138667
GitOrigin-RevId: 7978505a09d1af492360dc92f8b8a1d23f255a37
2 problems are fixed by this commit:
1) bad naming of `EditRunConfigurationsInNewUiAction` and its needlessness (IJ-CR-138667)
2) missing of actions in OldUi, which were reorganized by previous commits
To avoid duplication of "Edit..." items in Old UI that was solved before this commit by `EditRunConfigurationsInNewUiAction` implementation, the action with id `IdeActions.ACTION_EDIT_RUN_CONFIGURATIONS` is added under the corresponding condition in code after the commit. (After the completely removing of Old UI this part of changes can be reverted)
About the missing actions in Old UI:
They were missed because the DataContext did not contain a value for `RUN_CONFIGURATION_KEY` during actions updates. This is fixed by the introduced overridden `createActionPopup` method.
(cherry picked from commit 867e94bdedfdd753e783812d1939e22a3e37baa4)
IJ-CR-138667
GitOrigin-RevId: 86da724a6dac4218f392e91f4577e1458827635b
the new key-values in `ActionsBundle.properties` file are the copies of the corresponding `choose.run.popup.*` keys from `ExecutionBundle.properties`. The keys are renamed to the "action.[action_id].text/description" and moved to `ActionsBundle.properties` file so that they were automatically assigned to the corresponding actions declared in `LangActions.xml` file without writing any special code for doing this. The corresponding key-values were not removed from `ExecutionBundle.properties` because they have other usages. These usages were not rewritten so that they use the new key-values from `ActionsBundle.properties` because it can lead to changes in 100500 files, that can complicate possible backporting.
(cherry picked from commit 7ea94ef5f48a4dd323eb4cb33e149f772c0377f6)
IJ-CR-138667
GitOrigin-RevId: b9f345d1c3045151f5dcc335b0a0f654da408c42
... in Run Configiration executors menu and convert it into AnAction
(cherry picked from commit 608be4e8de2e2efe0490553dc3ead5987dc74060)
IJ-CR-138667
GitOrigin-RevId: 7f100be25f9970485a2dff9e81514bfa79043d02
1. inline outdated experimental registry options
2. use postprocessing to filter out unneeded actions
3. add all inline actions and let visibility logic do its job
4. extract `PinConfigurationAction` and make it work as a toggle
Prepare for
IJPL-61164 Ability to launch multiple configurations at once
GitOrigin-RevId: 99d018f3d0d6752933aef036a27a228a9b4bd5b7
A 4-value enum now includes previous "hard" and "soft" semantics without special treatment for `ToggleAction`.
See
IJPL-157628 Introduce Keep popups open for toggle items setting
GitOrigin-RevId: 123935b9367dd624b4c810b0dfa066fba23e1672
Add the ability to customize data contexts for delegates.
Session API is not used in case of customization. For now, session always uses the original data context.
GitOrigin-RevId: 4c4b7dcfe55d41ab708cba6a415272cecd8b8eb6
wrapping CreateRunConfiguration action spoils ConfigurationContext cache, so it's removed
hopefully this won't break scenarios described in IDEA-144385 (When JUnit run configuration exists it's hard to run main method in the same class)
GitOrigin-RevId: 4cf9d044c0e74a5fb2ccb134c379918181a8883f
