[AOSP-pick] Make run configurations configurable #7275
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry pick AOSP commit 990fdde7dae9cb0964c3e8339c3e8d6698b45e7e.
Let users control the IDE.
Allow breaking links between XML files and run configurations. It
often happens that one need to modify an imported configuration.
If syncing is disabled it won't be auto-updated by the sync unless
the link is re-enabled by the user.
Do not auto-detect the configuration handler every time the set of
selected build targets change. This may look like being helpful but
it is not obvious to users. Instead, the IDE should warn users about
incompatible run configuration handlers.
This will also prevent the IDE from corrupting run configurations
imported from XML files.
Keep auto-detecting the handler when the build targets are set for
the first time since run configuration syncing depends on this
behavior.
Allow users to choose the run configuration handler manually. It is
absolutely fine to just
build
and Android binary target and it isalso fine to attempt to deploy any other target. Most will fail but
some may be compatible rules.
In the future, add a button to detect the handler automatically,
which if needed can query blaze/depserver for the target kind if
unknown.
NOTE: This does not fix the issues itself and those run configurations
that failed to be imported correctly won't bew imported correctly
afterwards, however this change allows users to fix run
configurations themselves.
Bug: 382099213
Test: n/a (unfortunately)
Change-Id: I979a3cf9f32a0425b2732ee105212aef9985a0ab
AOSP: 990fdde7dae9cb0964c3e8339c3e8d6698b45e7e